These are the final results of the JSR Renewal Ballot for JSR #362. The EC has approved this ballot.
Special Vote Instructions
JSR 362 Status:
We have completed discussion about errata and minor improvements as compared to the JSR 286 Portlet Specification 2.0. In addition, we have decided on some of the main features for the 3.0 release, including an improved server-side state handling API that will ease portlet development and a client-side JavaScript API that will allow portlet programmers to use JavaScript code to update portlet parameters, execute portlet actions, and obtain portlet resources while remaining in an Ajax processing paradigm.
Progress has been slower that anticipated due to resource constraints, however, progress has been made. In order to prove that these concepts are feasible and to obtain feedback on them, we implemented a prototype based on the Apache Pluto Portlet Container reference implementation. The prototype is available from the Apache Pluto Git repository (branch: V3Prototype), and also in the form of a pre-deployed package that will run on Windows, located here:
https://java.net/projects/portletspec3/downloads/download/V3Prototype/V3Prototype-20150225.zip
The prototype implements all functionality discussed to date. The spec is now being updated to reflect these changes, and when finished, it will become the early draft for review.
Another point that has cost the group some cycles is that a potential CVE issue was discovered relating to the JSR 286 Portlet Specification 2.0. Deliberation of this issue was not documented in the meeting minutes, but is being done privately among EG members. After some deliberation, it was decided to publish a JSR 286 maintenance release and also produce an updated version of the portlet specification 2.0 jar file. This work is currently being performed.
thank you very much,
Martin Scott Nicklous
We have completed discussion about errata and minor improvements as compared to the JSR 286 Portlet Specification 2.0. In addition, we have decided on some of the main features for the 3.0 release, including an improved server-side state handling API that will ease portlet development and a client-side JavaScript API that will allow portlet programmers to use JavaScript code to update portlet parameters, execute portlet actions, and obtain portlet resources while remaining in an Ajax processing paradigm.
Progress has been slower that anticipated due to resource constraints, however, progress has been made. In order to prove that these concepts are feasible and to obtain feedback on them, we implemented a prototype based on the Apache Pluto Portlet Container reference implementation. The prototype is available from the Apache Pluto Git repository (branch: V3Prototype), and also in the form of a pre-deployed package that will run on Windows, located here:
https://java.net/projects/portletspec3/downloads/download/V3Prototype/V3Prototype-20150225.zip
The prototype implements all functionality discussed to date. The spec is now being updated to reflect these changes, and when finished, it will become the early draft for review.
Another point that has cost the group some cycles is that a potential CVE issue was discovered relating to the JSR 286 Portlet Specification 2.0. Deliberation of this issue was not documented in the meeting minutes, but is being done privately among EG members. After some deliberation, it was decided to publish a JSR 286 maintenance release and also produce an updated version of the portlet specification 2.0 jar file. This work is currently being performed.
Additional material is available from the following locations:
- JSR 362 Portlet Specification 3.0 Interface Working Document (Javadoc):
http://msnicklous.github.io/portletspec3/
- JSR 362 Portlet Specification 3.0 Working Document:
https://java.net/projects/portletspec3/downloads/download/WorkingDocs/PortletSpec3-20130726.pdf
- Wiki Article on Portlet Configuration:
https://java.net/projects/portletspec3/pages/PortletConfiguration
- Wiki Article on Portlet URLs:
https://java.net/projects/portletspec3/pages/PortletURLs
In summary, I believe the EG is making slow, but dedicated and steady progress, and I request Executive Committee approval for a renewal ballot that will allow us to continue this work.thank you very much,
Martin Scott Nicklous
Votes
EC
Arm Limited
Azul Systems, Inc.
Credit Suisse
Eclipse Foundation, Inc
Ericsson AB
Freescale Semiconductor
Fujitsu Limited
Gemalto M2M GmbH
Goldman Sachs & Co.
Hazelcast
Hewlett-Packard
IBM
Intel Corp.
Keil, Werner
London Java Community
Magnusson Jr, Geir
MicroDoc
Oracle
Red Hat
SAP SE
Software AG
SouJava
TOTVS
Twitter, Inc.
V2COM
