Modified: portals/site-live/pluto/v20/release-notes-2.0.0.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/release-notes-2.0.0.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v20/release-notes-2.0.0.html (original) +++ portals/site-live/pluto/v20/release-notes-2.0.0.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -254,266 +258,266 @@ The release notes of the previous release 1.1.7 are available here: <a href="../v11/release-notes.html">release notes 1.1.7</a>. </p> <div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-397"; class="externalLink">PLUTO-397</a>] - Copyright at bottom of Portal Driver content needs to be updated to 2007 +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-397";>PLUTO-397</a>] - Copyright at bottom of Portal Driver content needs to be updated to 2007 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-421"; class="externalLink">PLUTO-421</a>] - PortletRequest.getParameterMap() must return an unmodifiable map (PLT.11.1.1) +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-421";>PLUTO-421</a>] - PortletRequest.getParameterMap() must return an unmodifiable map (PLT.11.1.1) </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-430"; class="externalLink">PLUTO-430</a>] - Portlet Config changes +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-430";>PLUTO-430</a>] - Portlet Config changes </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-446"; class="externalLink">PLUTO-446</a>] - No way to set default page encoding for Pluto +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-446";>PLUTO-446</a>] - No way to set default page encoding for Pluto </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-448"; class="externalLink">PLUTO-448</a>] - No way to know if expiration cache value was set via PortletDD +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-448";>PLUTO-448</a>] - No way to know if expiration cache value was set via PortletDD </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-449"; class="externalLink">PLUTO-449</a>] - portlet-skin.jsp does not have the JSTL core taglib directive +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-449";>PLUTO-449</a>] - portlet-skin.jsp does not have the JSTL core taglib directive </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-450"; class="externalLink">PLUTO-450</a>] - ExternalAppScopedAttributeTest.jsp has a minor javascript error +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-450";>PLUTO-450</a>] - ExternalAppScopedAttributeTest.jsp has a minor javascript error </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-451"; class="externalLink">PLUTO-451</a>] - JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-451";>PLUTO-451</a>] - JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-452"; class="externalLink">PLUTO-452</a>] - Assembler ant task fails on WAR with no manifest +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-452";>PLUTO-452</a>] - Assembler ant task fails on WAR with no manifest </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-454"; class="externalLink">PLUTO-454</a>] - JSR-286 RI driver does not support more than one public render parameter +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-454";>PLUTO-454</a>] - JSR-286 RI driver does not support more than one public render parameter </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-455"; class="externalLink">PLUTO-455</a>] - Assembler emitts non-validating web.xml for servlet 2.3 and 2.4 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-455";>PLUTO-455</a>] - Assembler emitts non-validating web.xml for servlet 2.3 and 2.4 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-457"; class="externalLink">PLUTO-457</a>] - PortletContainerException doesn't chain Throwable +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-457";>PLUTO-457</a>] - PortletContainerException doesn't chain Throwable </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-462"; class="externalLink">PLUTO-462</a>] - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-462";>PLUTO-462</a>] - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-463"; class="externalLink">PLUTO-463</a>] - java.lang.ClassCastException: org.apache.pluto.internal.impl.PortletSessionImpl with Pluto 2.0 and Jetty +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-463";>PLUTO-463</a>] - java.lang.ClassCastException: org.apache.pluto.internal.impl.PortletSessionImpl with Pluto 2.0 and Jetty </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-466"; class="externalLink">PLUTO-466</a>] - Assembly code cannot parse Servlet 2.4 web.xml containing <jsp-config> tags +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-466";>PLUTO-466</a>] - Assembly code cannot parse Servlet 2.4 web.xml containing <jsp-config> tags </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-468"; class="externalLink">PLUTO-468</a>] - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-468";>PLUTO-468</a>] - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-469"; class="externalLink">PLUTO-469</a>] - Pluto Driver not using injected Portal URL Parser +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-469";>PLUTO-469</a>] - Pluto Driver not using injected Portal URL Parser </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-471"; class="externalLink">PLUTO-471</a>] - Assembler emitts non-validating web.xml for servlet 2.3 and 2.4 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-471";>PLUTO-471</a>] - Assembler emitts non-validating web.xml for servlet 2.3 and 2.4 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-473"; class="externalLink">PLUTO-473</a>] - XML Schema Location for pluto-portal-driver-config.xsd points to obsolete schema definition +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-473";>PLUTO-473</a>] - XML Schema Location for pluto-portal-driver-config.xsd points to obsolete schema definition </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-475"; class="externalLink">PLUTO-475</a>] - Default Portlet Skin and WindowStateAnchorTag emit invalid markup +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-475";>PLUTO-475</a>] - Default Portlet Skin and WindowStateAnchorTag emit invalid markup </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-476"; class="externalLink">PLUTO-476</a>] - Unused LocalStrings.properties with better messages +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-476";>PLUTO-476</a>] - Unused LocalStrings.properties with better messages </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-477"; class="externalLink">PLUTO-477</a>] - PortletRequestImpl throws a NullPointerException when getting USER_INFO for unauthenticated users +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-477";>PLUTO-477</a>] - PortletRequestImpl throws a NullPointerException when getting USER_INFO for unauthenticated users </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-478"; class="externalLink">PLUTO-478</a>] - Portlet Dispatching loses wrappers +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-478";>PLUTO-478</a>] - Portlet Dispatching loses wrappers </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-479"; class="externalLink">PLUTO-479</a>] - Pluto references internal (placeholder) wrapper classes instead of javax.portlet classes +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-479";>PLUTO-479</a>] - Pluto references internal (placeholder) wrapper classes instead of javax.portlet classes </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-480"; class="externalLink">PLUTO-480</a>] - Pluto resource response fails on forward because it checks for valid content type +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-480";>PLUTO-480</a>] - Pluto resource response fails on forward because it checks for valid content type </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-484"; class="externalLink">PLUTO-484</a>] - PortletURLImpl.setSecure() throws PortletSecurityException when PortletURLProvider.isSecureSupported() returns true +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-484";>PLUTO-484</a>] - PortletURLImpl.setSecure() throws PortletSecurityException when PortletURLProvider.isSecureSupported() returns true </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-490"; class="externalLink">PLUTO-490</a>] - Cannot deploy portlets to ROOT context +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-490";>PLUTO-490</a>] - Cannot deploy portlets to ROOT context </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-499"; class="externalLink">PLUTO-499</a>] - Invoking FilterConfig.getInitParameter() when there are no filter parameters defined results in NPE +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-499";>PLUTO-499</a>] - Invoking FilterConfig.getInitParameter() when there are no filter parameters defined results in NPE </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-505"; class="externalLink">PLUTO-505</a>] - Whitespace in PreferencesValidator declaration results in ClassNotFoundException +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-505";>PLUTO-505</a>] - Whitespace in PreferencesValidator declaration results in ClassNotFoundException </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-506"; class="externalLink">PLUTO-506</a>] - Invoking the store() method of PortletPreferences object results in NPE if no preferences declared in portlet.xml +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-506";>PLUTO-506</a>] - Invoking the store() method of PortletPreferences object results in NPE if no preferences declared in portlet.xml </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-507"; class="externalLink">PLUTO-507</a>] - PortalDriverFilter doesn't handle action requests properly, throws IllegalStateException +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-507";>PLUTO-507</a>] - PortalDriverFilter doesn't handle action requests properly, throws IllegalStateException </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-508"; class="externalLink">PLUTO-508</a>] - pluto2:install / pluto missing commons logging +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-508";>PLUTO-508</a>] - pluto2:install / pluto missing commons logging </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-509"; class="externalLink">PLUTO-509</a>] - JAXB portlet descriptor model handling broken with respect to the different namespace handling for portlet API 1.0 and 2.0 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-509";>PLUTO-509</a>] - JAXB portlet descriptor model handling broken with respect to the different namespace handling for portlet API 1.0 and 2.0 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-510"; class="externalLink">PLUTO-510</a>] - Web deployment descriptor model loading and rewriting broken and out-dated +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-510";>PLUTO-510</a>] - Web deployment descriptor model loading and rewriting broken and out-dated </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-511"; class="externalLink">PLUTO-511</a>] - Separate Pluto implementation from required interfaces in shared class loader +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-511";>PLUTO-511</a>] - Separate Pluto implementation from required interfaces in shared class loader </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-514"; class="externalLink">PLUTO-514</a>] - Invoking PortletRequest.isUserInRole() results in NPE if no <security-role-ref> elements defined +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-514";>PLUTO-514</a>] - Invoking PortletRequest.isUserInRole() results in NPE if no <security-role-ref> elements defined </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-515"; class="externalLink">PLUTO-515</a>] - Retrieving user information request attribute results in NPE if no <user-attribute> elements defined +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-515";>PLUTO-515</a>] - Retrieving user information request attribute results in NPE if no <user-attribute> elements defined </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-516"; class="externalLink">PLUTO-516</a>] - Pluto's PorletSessionImpl#setAttribute sometimes sets var into APPLICATION_SCOPE without explanation +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-516";>PLUTO-516</a>] - Pluto's PorletSessionImpl#setAttribute sometimes sets var into APPLICATION_SCOPE without explanation </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-517"; class="externalLink">PLUTO-517</a>] - PortletWindowConfig#createPortletId generates troublesome id with leading slash +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-517";>PLUTO-517</a>] - PortletWindowConfig#createPortletId generates troublesome id with leading slash </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-522"; class="externalLink">PLUTO-522</a>] - pluto looks up wrong context when publish an event in response to an event +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-522";>PLUTO-522</a>] - pluto looks up wrong context when publish an event in response to an event </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-527"; class="externalLink">PLUTO-527</a>] - FilterConfig.getInitParameterNames() is not implemented +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-527";>PLUTO-527</a>] - FilterConfig.getInitParameterNames() is not implemented </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-528"; class="externalLink">PLUTO-528</a>] - PortletContextManager registers portlets only if log level info is enabled +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-528";>PLUTO-528</a>] - PortletContextManager registers portlets only if log level info is enabled </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-529"; class="externalLink">PLUTO-529</a>] - PortletRequest/PortletResponse implementations extending HttpServletRequest/Response wrappers causes "indentity" problems when accessed from servlets +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-529";>PLUTO-529</a>] - PortletRequest/PortletResponse implementations extending HttpServletRequest/Response wrappers causes "indentity" problems when accessed from servlets </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-530"; class="externalLink">PLUTO-530</a>] - RequestDispatcher path query string parameter handling too limited and broken with nested dispatches +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-530";>PLUTO-530</a>] - RequestDispatcher path query string parameter handling too limited and broken with nested dispatches </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-535"; class="externalLink">PLUTO-535</a>] - Dispatched HttpServletRequest path info methods must return path information used to obtain the PortletRequestDispatcher +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-535";>PLUTO-535</a>] - Dispatched HttpServletRequest path info methods must return path information used to obtain the PortletRequestDispatcher </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-536"; class="externalLink">PLUTO-536</a>] - Setting the ResourceResponse character encoding requires to support locale-encoding-mapping-list from web.xml +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-536";>PLUTO-536</a>] - Setting the ResourceResponse character encoding requires to support locale-encoding-mapping-list from web.xml </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-541"; class="externalLink">PLUTO-541</a>] - locale retrieval from PortletRequestImpl throws NoSuchElement Exception +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-541";>PLUTO-541</a>] - locale retrieval from PortletRequestImpl throws NoSuchElement Exception </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-553"; class="externalLink">PLUTO-553</a>] - commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-553";>PLUTO-553</a>] - commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-554"; class="externalLink">PLUTO-554</a>] - Infinite invocation when a view page of a portlet tries to include some result from other servlet path. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-554";>PLUTO-554</a>] - Infinite invocation when a view page of a portlet tries to include some result from other servlet path. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-557"; class="externalLink">PLUTO-557</a>] - Fixing the RequestDispatcher implementation to be more web container generic and pluggable through a Service +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-557";>PLUTO-557</a>] - Fixing the RequestDispatcher implementation to be more web container generic and pluggable through a Service </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-561"; class="externalLink">PLUTO-561</a>] - ResourceResponse.setContentType() with charset is broken. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-561";>PLUTO-561</a>] - ResourceResponse.setContentType() with charset is broken. </li> </ul> </div> <div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-360"; class="externalLink">PLUTO-360</a>] - FileAssemblerTest cannot be executed offline +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-360";>PLUTO-360</a>] - FileAssemblerTest cannot be executed offline </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-395"; class="externalLink">PLUTO-395</a>] - Copy assembly module from trunk to 286-COMPATIBILITY branch +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-395";>PLUTO-395</a>] - Copy assembly module from trunk to 286-COMPATIBILITY branch </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-417"; class="externalLink">PLUTO-417</a>] - PortletResponseImpl doesn't allow wsrp rewrite urls +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-417";>PLUTO-417</a>] - PortletResponseImpl doesn't allow wsrp rewrite urls </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-428"; class="externalLink">PLUTO-428</a>] - Refactoring ResponseImpl +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-428";>PLUTO-428</a>] - Refactoring ResponseImpl </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-429"; class="externalLink">PLUTO-429</a>] - Refactoring. Elemenate multiple code in *ResponseImpl. Extract same code in new Superclass. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-429";>PLUTO-429</a>] - Refactoring. Elemenate multiple code in *ResponseImpl. Extract same code in new Superclass. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-442"; class="externalLink">PLUTO-442</a>] - Create a Testsuite for JSR-286 features +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-442";>PLUTO-442</a>] - Create a Testsuite for JSR-286 features </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-445"; class="externalLink">PLUTO-445</a>] - Patch to implement mime response cache control +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-445";>PLUTO-445</a>] - Patch to implement mime response cache control </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-456"; class="externalLink">PLUTO-456</a>] - fix line endings on files. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-456";>PLUTO-456</a>] - fix line endings on files. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-458"; class="externalLink">PLUTO-458</a>] - Improve exception handling with AbstractCastorDescriptorService +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-458";>PLUTO-458</a>] - Improve exception handling with AbstractCastorDescriptorService </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-459"; class="externalLink">PLUTO-459</a>] - Update 286's pom to use Java 1.5 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-459";>PLUTO-459</a>] - Update 286's pom to use Java 1.5 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-481"; class="externalLink">PLUTO-481</a>] - Pluto 2.0 Refactoring Initiative +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-481";>PLUTO-481</a>] - Pluto 2.0 Refactoring Initiative </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-487"; class="externalLink">PLUTO-487</a>] - PortletPreferencesImpl should not store the preferences every time it is instantiated +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-487";>PLUTO-487</a>] - PortletPreferencesImpl should not store the preferences every time it is instantiated </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-488"; class="externalLink">PLUTO-488</a>] - When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-488";>PLUTO-488</a>] - When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-489"; class="externalLink">PLUTO-489</a>] - Refactor request attribute handling into optional service interface +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-489";>PLUTO-489</a>] - Refactor request attribute handling into optional service interface </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-491"; class="externalLink">PLUTO-491</a>] - Attach source jars to maven deployed artifacts +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-491";>PLUTO-491</a>] - Attach source jars to maven deployed artifacts </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-492"; class="externalLink">PLUTO-492</a>] - Duplicate web site code in pluto-site module and root src dir +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-492";>PLUTO-492</a>] - Duplicate web site code in pluto-site module and root src dir </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-495"; class="externalLink">PLUTO-495</a>] - Eclipse autobuilld/compile/debug project +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-495";>PLUTO-495</a>] - Eclipse autobuilld/compile/debug project </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-503"; class="externalLink">PLUTO-503</a>] - Expose createPortletScopedId and isInCurrentPortletScope of PortletSessionImpl as protected +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-503";>PLUTO-503</a>] - Expose createPortletScopedId and isInCurrentPortletScope of PortletSessionImpl as protected </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-504"; class="externalLink">PLUTO-504</a>] - Create PortletSession via PortletEnvironmentService +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-504";>PLUTO-504</a>] - Create PortletSession via PortletEnvironmentService </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-512"; class="externalLink">PLUTO-512</a>] - improve error logging diagnostics when inputstream == null +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-512";>PLUTO-512</a>] - improve error logging diagnostics when inputstream == null </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-519"; class="externalLink">PLUTO-519</a>] - Better error msg on invalid event payload class +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-519";>PLUTO-519</a>] - Better error msg on invalid event payload class </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-520"; class="externalLink">PLUTO-520</a>] - Provide backwards compatiblity for Portlet Applications using/embedding Pluto 1.0.1 portlet.tld +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-520";>PLUTO-520</a>] - Provide backwards compatiblity for Portlet Applications using/embedding Pluto 1.0.1 portlet.tld </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-521"; class="externalLink">PLUTO-521</a>] - add warning when trying to publish an event when event not registered +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-521";>PLUTO-521</a>] - add warning when trying to publish an event when event not registered </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-531"; class="externalLink">PLUTO-531</a>] - New PortletRequestStateService SPI to replace and extend most of the currrent incorrect used PropertyManager SPI and PortletURLProvider SPI +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-531";>PLUTO-531</a>] - New PortletRequestStateService SPI to replace and extend most of the currrent incorrect used PropertyManager SPI and PortletURLProvider SPI </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-532"; class="externalLink">PLUTO-532</a>] - New PortletResponseStateProvider SPI +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-532";>PLUTO-532</a>] - New PortletResponseStateProvider SPI </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-538"; class="externalLink">PLUTO-538</a>] - New EventCoordinationService and merging EventContainer with PortletContainer +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-538";>PLUTO-538</a>] - New EventCoordinationService and merging EventContainer with PortletContainer </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-539"; class="externalLink">PLUTO-539</a>] - New FilterManagerService implementation +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-539";>PLUTO-539</a>] - New FilterManagerService implementation </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-540"; class="externalLink">PLUTO-540</a>] - New PortletURLListenerService +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-540";>PLUTO-540</a>] - New PortletURLListenerService </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-544"; class="externalLink">PLUTO-544</a>] - Element creation in PortletResponse needs to be moved into PortletResponseContext. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-544";>PLUTO-544</a>] - Element creation in PortletResponse needs to be moved into PortletResponseContext. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-545"; class="externalLink">PLUTO-545</a>] - Separate driver interfaces/classes from container (api) +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-545";>PLUTO-545</a>] - Separate driver interfaces/classes from container (api) </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-546"; class="externalLink">PLUTO-546</a>] - Improve Maven Usage +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-546";>PLUTO-546</a>] - Improve Maven Usage </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-547"; class="externalLink">PLUTO-547</a>] - Remove distinction between required and optional container services +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-547";>PLUTO-547</a>] - Remove distinction between required and optional container services </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-548"; class="externalLink">PLUTO-548</a>] - Move portlet apis to own svn location +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-548";>PLUTO-548</a>] - Move portlet apis to own svn location </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-549"; class="externalLink">PLUTO-549</a>] - Rename PortletInvokerService METHOD_NOOP to METHOD_LOAD +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-549";>PLUTO-549</a>] - Rename PortletInvokerService METHOD_NOOP to METHOD_LOAD </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-550"; class="externalLink">PLUTO-550</a>] - Change the FilterManager interface to have a separate method for each lifecycle +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-550";>PLUTO-550</a>] - Change the FilterManager interface to have a separate method for each lifecycle </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-551"; class="externalLink">PLUTO-551</a>] - Remove class loader from filter manager interface +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-551";>PLUTO-551</a>] - Remove class loader from filter manager interface </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-558"; class="externalLink">PLUTO-558</a>] - Change FilterManagerService to use portlet entity +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-558";>PLUTO-558</a>] - Change FilterManagerService to use portlet entity </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-559"; class="externalLink">PLUTO-559</a>] - Drop PortletEntity interface +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-559";>PLUTO-559</a>] - Drop PortletEntity interface </li> </ul> </div> <div class="section"><h3><a name="New_Feature"></a>New Feature</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-263"; class="externalLink">PLUTO-263</a>] - add Resource Serving +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-263";>PLUTO-263</a>] - add Resource Serving </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-267"; class="externalLink">PLUTO-267</a>] - Implementation of the new Eventing Model +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-267";>PLUTO-267</a>] - Implementation of the new Eventing Model </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-337"; class="externalLink">PLUTO-337</a>] - Add JAXB object payload delivering +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-337";>PLUTO-337</a>] - Add JAXB object payload delivering </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-371"; class="externalLink">PLUTO-371</a>] - Portlet Filter +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-371";>PLUTO-371</a>] - Portlet Filter </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-415"; class="externalLink">PLUTO-415</a>] - Update from Spec rev 22 to 23 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-415";>PLUTO-415</a>] - Update from Spec rev 22 to 23 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-418"; class="externalLink">PLUTO-418</a>] - Add support for container-runtime-options +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-418";>PLUTO-418</a>] - Add support for container-runtime-options </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-423"; class="externalLink">PLUTO-423</a>] - PortletRequestDispatcher implementation for Spec Chapter 19 "Dispatching Requests to Servlets and JSPs" +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-423";>PLUTO-423</a>] - PortletRequestDispatcher implementation for Spec Chapter 19 "Dispatching Requests to Servlets and JSPs" </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-424"; class="externalLink">PLUTO-424</a>] - Support for CCPPProfileService (with DummyImplementation) +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-424";>PLUTO-424</a>] - Support for CCPPProfileService (with DummyImplementation) </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-425"; class="externalLink">PLUTO-425</a>] - Implementation of GetLifecyclePhase +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-425";>PLUTO-425</a>] - Implementation of GetLifecyclePhase </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-431"; class="externalLink">PLUTO-431</a>] - PortletUrl listener +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-431";>PLUTO-431</a>] - PortletUrl listener </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-433"; class="externalLink">PLUTO-433</a>] - taglib +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-433";>PLUTO-433</a>] - taglib </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-513"; class="externalLink">PLUTO-513</a>] - Support portlet managed custom modes as defined in PLT.8.4 of JSR-286 spec +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-513";>PLUTO-513</a>] - Support portlet managed custom modes as defined in PLT.8.4 of JSR-286 spec </li> </ul> </div> <div class="section"><h3><a name="Task"></a>Task</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-373"; class="externalLink">PLUTO-373</a>] - Throw exception if event value has not a valid JAXB binding or is not a Java primitive type +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-373";>PLUTO-373</a>] - Throw exception if event value has not a valid JAXB binding or is not a Java primitive type </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-402"; class="externalLink">PLUTO-402</a>] - Merge SVN trunk with 1.1-286-COMPATIBILITY branch using 1.1-286-trunk-merge branch +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-402";>PLUTO-402</a>] - Merge SVN trunk with 1.1-286-COMPATIBILITY branch using 1.1-286-trunk-merge branch </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-483"; class="externalLink">PLUTO-483</a>] - Pluto 2.0 refactoring TODO tasks +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-483";>PLUTO-483</a>] - Pluto 2.0 refactoring TODO tasks </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-523"; class="externalLink">PLUTO-523</a>] - Further abstractions of the Pluto SPI to support embedding in and extending by other portals +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-523";>PLUTO-523</a>] - Further abstractions of the Pluto SPI to support embedding in and extending by other portals </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-537"; class="externalLink">PLUTO-537</a>] - Cleaning up Pluto packages +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-537";>PLUTO-537</a>] - Cleaning up Pluto packages </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-552"; class="externalLink">PLUTO-552</a>] - Change Pluto 2.0 maven groupid to org.apache.portals.pluto +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-552";>PLUTO-552</a>] - Change Pluto 2.0 maven groupid to org.apache.portals.pluto </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-560"; class="externalLink">PLUTO-560</a>] - Change Pluto 2.0 maven pluto plugin prefix from pluto to pluto2 to prevent lookup clashes with the Pluto 1.x plugin +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-560";>PLUTO-560</a>] - Change Pluto 2.0 maven pluto plugin prefix from pluto to pluto2 to prevent lookup clashes with the Pluto 1.x plugin </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-562"; class="externalLink">PLUTO-562</a>] - Replace dependency on JCP provided JSR-286 portlet-api-2.0 with Apache Portals maintained portlet-api_2.0_spec-1.0 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-562";>PLUTO-562</a>] - Replace dependency on JCP provided JSR-286 portlet-api-2.0 with Apache Portals maintained portlet-api_2.0_spec-1.0 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-563"; class="externalLink">PLUTO-563</a>] - Move Pluto site project structure outside trunk to a new sub site project of the main Portals site project +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-563";>PLUTO-563</a>] - Move Pluto site project structure outside trunk to a new sub site project of the main Portals site project </li> </ul> </div> <div class="section"><h3><a name="Sub-task"></a>Sub-task</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-403"; class="externalLink">PLUTO-403</a>] - Merge maven-pluto-plugin code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-404"; class="externalLink">PLUTO-404</a>] - Merge pluto-container code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-405"; class="externalLink">PLUTO-405</a>] - Merge pluto-portal-driver code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-406"; class="externalLink">PLUTO-406</a>] - Merge pluto-portal-driver-impl code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-407"; class="externalLink">PLUTO-407</a>] - Merge pluto-portal code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-408"; class="externalLink">PLUTO-408</a>] - Merge pluto-taglib code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-409"; class="externalLink">PLUTO-409</a>] - Merge pluto-testsuite code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-410"; class="externalLink">PLUTO-410</a>] - Merge pluto-util code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-411"; class="externalLink">PLUTO-411</a>] - Merge pluto-descriptor-api code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-412"; class="externalLink">PLUTO-412</a>] - Merge pluto-ant-tasks code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-413"; class="externalLink">PLUTO-413</a>] - Merge pluto-descriptor-impl code from trunk to 1.1-286-trunk-merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-416"; class="externalLink">PLUTO-416</a>] - Fix failure of JaxBDescriptorServiceImplTest unit test in 1.1-286-trunk merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-419"; class="externalLink">PLUTO-419</a>] - Fix failure of FileAssemblerTest unit test in 1.1-286-trunk merge branch</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-443"; class="externalLink">PLUTO-443</a>] - Add resource serving tests to testsuite for JSR-286</li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-444"; class="externalLink">PLUTO-444</a>] - Filter chain is not implemented the right way</li> +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-403";>PLUTO-403</a>] - Merge maven-pluto-plugin code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-404";>PLUTO-404</a>] - Merge pluto-container code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-405";>PLUTO-405</a>] - Merge pluto-portal-driver code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-406";>PLUTO-406</a>] - Merge pluto-portal-driver-impl code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-407";>PLUTO-407</a>] - Merge pluto-portal code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-408";>PLUTO-408</a>] - Merge pluto-taglib code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-409";>PLUTO-409</a>] - Merge pluto-testsuite code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-410";>PLUTO-410</a>] - Merge pluto-util code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-411";>PLUTO-411</a>] - Merge pluto-descriptor-api code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-412";>PLUTO-412</a>] - Merge pluto-ant-tasks code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-413";>PLUTO-413</a>] - Merge pluto-descriptor-impl code from trunk to 1.1-286-trunk-merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-416";>PLUTO-416</a>] - Fix failure of JaxBDescriptorServiceImplTest unit test in 1.1-286-trunk merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-419";>PLUTO-419</a>] - Fix failure of FileAssemblerTest unit test in 1.1-286-trunk merge branch</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-443";>PLUTO-443</a>] - Add resource serving tests to testsuite for JSR-286</li> +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-444";>PLUTO-444</a>] - Filter chain is not implemented the right way</li> </ul> </div> <div class="section"><h3><a name="Test"></a>Test</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-366"; class="externalLink">PLUTO-366</a>] - Add eventing tests to testsuite for JSR-286 +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-366";>PLUTO-366</a>] - Add eventing tests to testsuite for JSR-286 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-367"; class="externalLink">PLUTO-367</a>] - Add public render parameters tests to testsuite for JSR-286 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-367";>PLUTO-367</a>] - Add public render parameters tests to testsuite for JSR-286 </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-368"; class="externalLink">PLUTO-368</a>] - Add portlet filter tests to testsuite for JSR-286 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-368";>PLUTO-368</a>] - Add portlet filter tests to testsuite for JSR-286 </li> </ul> </div> <div class="section"><h3><a name="Wish"></a>Wish</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/JS2-786"; class="externalLink">JS2-786</a>] - Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages</li> +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/JS2-786";>JS2-786</a>] - Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages</li> </ul> </div> </div>
Modified: portals/site-live/pluto/v20/release-notes-2.0.1.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/release-notes-2.0.1.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v20/release-notes-2.0.1.html (original) +++ portals/site-live/pluto/v20/release-notes-2.0.1.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -254,24 +258,24 @@ The release notes of the previous release 2.0.0 are available here: <a href="release-notes-2.0.0.html">release notes 2.0.0</a>. </p> <div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-564"; class="externalLink">PLUTO-564</a>] - Configuration errors are not much descriptive (II Part) +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-564";>PLUTO-564</a>] - Configuration errors are not much descriptive (II Part) </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-565"; class="externalLink">PLUTO-565</a>] - Resource config not found under /WEB-INF/ +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-565";>PLUTO-565</a>] - Resource config not found under /WEB-INF/ </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-566"; class="externalLink">PLUTO-566</a>] - Pluto portal does not include dependency of pluto-taglib needed to run jsp +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-566";>PLUTO-566</a>] - Pluto portal does not include dependency of pluto-taglib needed to run jsp </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-568"; class="externalLink">PLUTO-568</a>] - Request attributes with javax not getting namespaced and hence colliding +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-568";>PLUTO-568</a>] - Request attributes with javax not getting namespaced and hence colliding </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-585"; class="externalLink">PLUTO-585</a>] - Make pluto more osgi friendly +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-585";>PLUTO-585</a>] - Make pluto more osgi friendly </li> </ul> </div> <div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-567"; class="externalLink">PLUTO-567</a>] - Make Pluto work even if main portlets are not available. +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-567";>PLUTO-567</a>] - Make Pluto work even if main portlets are not available. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-580"; class="externalLink">PLUTO-580</a>] - Allow portlet descriptor with empty namespace during deployment. +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-580";>PLUTO-580</a>] - Allow portlet descriptor with empty namespace during deployment. </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-586"; class="externalLink">PLUTO-586</a>] - Simplify POM release profile +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-586";>PLUTO-586</a>] - Simplify POM release profile </li> </ul> </div> Modified: portals/site-live/pluto/v20/release-notes-2.0.2.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/release-notes-2.0.2.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v20/release-notes-2.0.2.html (original) +++ portals/site-live/pluto/v20/release-notes-2.0.2.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -254,21 +258,21 @@ The release notes of the previous release 2.0.1 are available here: <a href="release-notes-2.0.1.html">release notes 2.0.1</a>. </p> <div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-569"; class="externalLink">PLUTO-569</a>] - Threading issue in DefaulltPortletInvoker +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-569";>PLUTO-569</a>] - Threading issue in DefaulltPortletInvoker </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-575"; class="externalLink">PLUTO-575</a>] - Javascript fails to correctly clear out select boxes +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-575";>PLUTO-575</a>] - Javascript fails to correctly clear out select boxes </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-581"; class="externalLink">PLUTO-581</a>] - org.apache.pluto.driver.url.impl.PortalURLParserImpl not properly decoding public/private render parameters +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-581";>PLUTO-581</a>] - org.apache.pluto.driver.url.impl.PortalURLParserImpl not properly decoding public/private render parameters </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-583"; class="externalLink">PLUTO-583</a>] - PortalURLParserImpl: unnecessary "?" +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-583";>PLUTO-583</a>] - PortalURLParserImpl: unnecessary "?" </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-590"; class="externalLink">PLUTO-590</a>] - Nested dispatching from a portlet to two or more servlet/jsps does not retain the portlet contextPath when calling (servlet)request.getContextPath() but returns the portal contextPath +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-590";>PLUTO-590</a>] - Nested dispatching from a portlet to two or more servlet/jsps does not retain the portlet contextPath when calling (servlet)request.getContextPath() but returns the portal contextPath </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-591"; class="externalLink">PLUTO-591</a>] - HttpServletPortletResponseWrapper incorrectly assumes MimeResponse.getPortletOutputStream() is upcastable to ServletOutputStream +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-591";>PLUTO-591</a>] - HttpServletPortletResponseWrapper incorrectly assumes MimeResponse.getPortletOutputStream() is upcastable to ServletOutputStream </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-593"; class="externalLink">PLUTO-593</a>] - Will not load portlets deployed in root servlet context +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-593";>PLUTO-593</a>] - Will not load portlets deployed in root servlet context </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-594"; class="externalLink">PLUTO-594</a>] - pluto-container-api-xxx.jar needs to include Specification-Version +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-594";>PLUTO-594</a>] - pluto-container-api-xxx.jar needs to include Specification-Version </li> </ul> </div> Modified: portals/site-live/pluto/v20/release-notes.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/release-notes.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v20/release-notes.html (original) +++ portals/site-live/pluto/v20/release-notes.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -254,20 +258,20 @@ The release notes of the previous release 2.0.2 are available here: <a href="release-notes-2.0.2.html">release notes 2.0.2</a>. </p> <div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-598"; class="externalLink">PLUTO-598</a>] - Retrieving Portlet invoked servlet request attributes should first check PortletRequest attributes before using fallback to the web container +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-598";>PLUTO-598</a>] - Retrieving Portlet invoked servlet request attributes should first check PortletRequest attributes before using fallback to the web container </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-599"; class="externalLink">PLUTO-599</a>] - ResourceURLTag286 ignores javax.portlet.escapeXml +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-599";>PLUTO-599</a>] - ResourceURLTag286 ignores javax.portlet.escapeXml </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-609"; class="externalLink">PLUTO-609</a>] - PortletPreferencesImpl doesn't handle null preferences correctly +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-609";>PLUTO-609</a>] - PortletPreferencesImpl doesn't handle null preferences correctly </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-610"; class="externalLink">PLUTO-610</a>] - RenderURLTag168 incorrectly extends PortletURLTag286 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-610";>PLUTO-610</a>] - RenderURLTag168 incorrectly extends PortletURLTag286 </li> </ul> </div> <div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li>[<a href="https://issues.apache.org/jira/browse/PLUTO-601"; class="externalLink">PLUTO-601</a>] - Remove expensive object creation in PortletAppDescriptorServiceImpl +<ul><li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-601";>PLUTO-601</a>] - Remove expensive object creation in PortletAppDescriptorServiceImpl </li> -<li>[<a href="https://issues.apache.org/jira/browse/PLUTO-611"; class="externalLink">PLUTO-611</a>] - Upgrade binary distribution to use latest Tomcat 7.0.21 +<li>[<a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-611";>PLUTO-611</a>] - Upgrade binary distribution to use latest Tomcat 7.0.21 </li> </ul> </div> Modified: portals/site-live/pluto/v30/deploying.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v30/deploying.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v30/deploying.html (original) +++ portals/site-live/pluto/v30/deploying.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -317,10 +321,8 @@ <render-config default="Test Page"> ... ... <page name="Your Portal Page Name" uri="/WEB-INF/themes/pluto-default-theme.jsp"> - <portlet context="/your_portlet_app_context_path" - name="your_portlet_1"/> - <portlet context="/your_portlet_app_context_path" - name="your_portlet_2"/> + <portlet context="/your_portlet_app_context_path" name="your_portlet_1"/> + <portlet context="/your_portlet_app_context_path" name="your_portlet_2"/> </page> </render-config> </pre> Modified: portals/site-live/pluto/v30/getting-started.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v30/getting-started.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v30/getting-started.html (original) +++ portals/site-live/pluto/v30/getting-started.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -262,7 +266,7 @@ <ol type="1"><li> Download the Pluto 3.0 binary distribution named <strong>pluto-current-bundle</strong> from - a <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/"; class="externalLink">distribution site</a>.</li> + a <a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/pluto/";>distribution site</a>.</li> <li>Unzip the binary distribution into a directory.</li> <ol type="1"><li>pluto-<version> (pluto-3.0) will be the top level directory.</li> </ol> @@ -273,7 +277,7 @@ Use shutdown.bat/shutdown.sh to stop the portal </li> <li> - Browse to <a href="http://localhost:8080/pluto/portal"; class="externalLink">http://localhost:8080/pluto/portal</a></li> + Browse to <a class="externalLink" href="http://localhost:8080/pluto/portal";>http://localhost:8080/pluto/portal</a></li> <li> Login as user pluto (password=pluto) or tomcat (password=pluto). </li> @@ -287,7 +291,7 @@ </p> <p> The Pluto project uses the - <a href="https://git-scm.com/"; class="externalLink">Git</a> version control + <a class="externalLink" href="https://git-scm.com/";>Git</a> version control system. If you're new to Git, you can find many books and online resources to help you. </p> @@ -298,25 +302,25 @@ the packages, please access the appropriate web resources. <ul><li> A Java runtime environment, version 1.7.0 or later. See - <a href="https://java.com/en/download/"; class="externalLink">the Java download site</a></li> + <a class="externalLink" href="https://java.com/en/download/";>the Java download site</a></li> <li> Apache Ant, version 1.9.3 or later. See - <a href="https://ant.apache.org/bindownload.cgi"; class="externalLink">the Apache Ant download site</a></li> + <a class="externalLink" href="https://ant.apache.org/bindownload.cgi";>the Apache Ant download site</a></li> <li> Apache Maven, version 3.3.1 or later. See - <a href="https://maven.apache.org/download.cgi"; class="externalLink">the Apache Maven download site</a></li> + <a class="externalLink" href="https://maven.apache.org/download.cgi";>the Apache Maven download site</a></li> <li> Git version control software, version 2.0.0 or later. See - <a href="https://git-scm.com/downloads"; class="externalLink">the Git download site</a></li> + <a class="externalLink" href="https://git-scm.com/downloads";>the Git download site</a></li> </ul> Note that your computer will also require access to the Internet during the build process in order to access maven repositories and other information. </p> -<h4>Obtaining Pluto 3.0 Source Code"</h4> +<h4>Obtaining Pluto 3.0 Source Code</h4> <p> To browse the Pluto source code online, access - <a href="https://github.com/apache/portals-pluto"; class="externalLink">the Apache Pluto Github mirror.</a> + <a class="externalLink" href="https://github.com/apache/portals-pluto";>the Apache Pluto Github mirror.</a> This is current at all times. </p> <h4>Cloning the Pluto Repository</h4> Modified: portals/site-live/pluto/v30/portlet-api.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v30/portlet-api.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v30/portlet-api.html (original) +++ portals/site-live/pluto/v30/portlet-api.html Fri Dec 2 14:16:01 2016 @@ -13,7 +13,7 @@ <html xmlns="http://www.w3.org/1999/xhtml";> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Pluto - Portlet API version 3.0 Overview</title> + <title>Pluto - Portlet Concepts</title> <style type="text/css" media="all"> @import url("../css/maven-base.css"); @import url("../css/maven-theme.css"); @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,10 +144,14 @@ </li> <li class="none"> - <strong>Portlet API 3.0</strong> + <strong>Portlet Concepts</strong> </li> <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> + </li> + + <li class="none"> <a href="../v30/tck.html">Using the TCK</a> </li> @@ -246,22 +250,121 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Portlet_API_version_3.0_Overview"></a>Portlet API version 3.0 Overview</h2> + <div class="section"><h2><a name="Portlet_Concepts"></a>Portlet Concepts</h2> +<div class="section"><h3><a name="The_Portlet_Phase_Model"></a>The Portlet Phase Model</h3> +<p> + When a request arrives at a portal targeted to a portlet, the portlet container + executes portlet code according to a phase model. + </p> +<img src="../images/phaseModel.png" /><p> + There are three processing stages containing five processing phases, defined as follows: + </p> +<p> + The portlet API allows creation of URLs that can be included into portlet + markup in order to activate the portlet processing stages. + </p> +<ul><li> + The Action URL, or Partial Action URL triggers preparation stage processing. + </li> +<li> + The Render URL triggers aggregation stage processing. + </li> +<li> + The Resource URL triggers resourec stage processing. + </li> +</ul> +<p> + When a stage is triggered, the processing phases within that stage are executed. + </p> +<dl><dt> + Action Phase + </dt> +<dd> + The portlet can perform updates and set up render state for the Aggregation Stage. + The action phase is initiated thru form post targeting the portlet. + During action phase processing, the portlet can fire events, resulting in event phase processing. + </dd> +<dt> + Event Phase + </dt> +<dd> + During event phase processing, the portlet container routes any fired events to + the portlets subscribed to the events. + Portlets define the events they can fire and receive through configuration. + </dd> +<dt> + Header Phase (new with V3): + </dt> +<dd> + Called for all portlets before the overall portal response is committed. + Portlets can contribute header values, cookies, and markup for the HEAD section + and can declare page resource dependencies. + </dd> +<dt> + Render Phase: + </dt> +<dd> + Called after the header phase for all portlets has been executed. + The portlet generates its markup for aggregation into the portal page. + During the render phase, the portlet may only generate markup that the portal + is able to integrate into the portal page. + </dd> +<dt> + Resource Stage + </dt> +<dd> + Initiated by an Ajax request from portlet JavaScript code using a resource URL. + During the resource phase, the portlet has nearly complete control over + the response returned to the client. + It may produce markup, JSON data, or binary data, for example. + </dd> +</dl> <p> - JSR 362 Portlet Specification 3.0 introduces many improvements to the - portlet programming model. It adds configuration through annotation, - asynchronous support similar to the servlet asynchronous support, - multipart form support, support for CDI beans, method annotation support - allowing portlet methods to reside in different classes, and a JavaScript - API that allows portal pages to function as single-page applications. The - Pluto 3.0 portlet container implements all JSR 362 features and passes the - TCK. While doing so, Pluto 3.0 remains fully compliant to the 2.0 Portlet - Specification, meaning that version 2.0 portlets can run on the version - 3.0 portlet container. - </p> + The portlet container drives portlet phase execution + by setting up the execution environment for each portlet and phase and + calling the corresponding portlet lifecycle methods. + </p> <p> - To be continued ... - </p> + The portlet participates in the phase model + by implementing the corresponding lifecycle methods + and by using the portlet API to carry out the appropriate tasks. + </p> +</div> +<div class="section"><h3><a name="The_Portlet_Lifecyce_Methods"></a>The Portlet Lifecyce Methods</h3> +<img src="../images/lifecycleMethods.png" /><p> + Each portlet phase has a corresponding lifecycle method. + The portlet container executes the prrocessing phase by calling the portlet lifecycle method. + Each phase is provided with specific request and response objects. + Methods can implemented using the interfaces + <code>Portlet, ResourceServingPortlet, EventPortlet</code> and <code>HeaderPortlet</code>. + Portlets can be configured through annotation or using the portlet deployment descriptor. + </p> +<p> + Portlets can implement the lifecycle methods by extending the GenericPortlet class + or by using the extended method annotations. + </p> +<p> + When the extended method annotations are used, portlet lifecycle methods can be arbitrary methods in java classes. + The methods are identified by the portlet lifecycle method annotations and have + relaxed method signature requirements as compared to interface methods. + When the method annotations are used, portlets are implicitly configured if no + data beyond that provided in the annotation is required. + Additional configuration is possible through annotation or portlet deployment descriptor. + </p> +<ul><li> + Set up / tear down: @InitMethod, @DestroyMethod + </li> +<li> + Preparation stage: @ActionMethod, @EventMethod, + </li> +<li> + Aggregation stage: @HeaderMethod, @RenderMethod, + </li> +<li> + Resource stage: @ServeResourceMethod + </li> +</ul> +</div> </div> </div> Modified: portals/site-live/pluto/v30/release-notes.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v30/release-notes.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v30/release-notes.html (original) +++ portals/site-live/pluto/v30/release-notes.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -252,12 +256,6 @@ implementation of JSR 362 Portlet Specification 3.0. </p> <p></p> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li></li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -</div> </div> </div> Modified: portals/site-live/pluto/v30/tck.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v30/tck.html?rev=1772349&r1=1772348&r2=1772349&view=diff ============================================================================== --- portals/site-live/pluto/v30/tck.html (original) +++ portals/site-live/pluto/v30/tck.html Fri Dec 2 14:16:01 2016 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2016-12-01 + Last Published: 2016-12-02 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -144,7 +144,11 @@ </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet API 3.0</a> + <a href="../v30/portlet-api.html">Portlet Concepts</a> + </li> + + <li class="none"> + <a href="../v30/v3Features.html">Version 3 Features</a> </li> <li class="none"> @@ -335,6 +339,244 @@ success or failure. </p> </div> +<div class="section"><h3><a name="Project_Structure"></a>Project Structure</h3> +<p> + The TCK source code is located in the subdirectory <code>./pluto/portlet-tck_3.0</code>. + The project consists of the following modules: + </p> +<dl><dt> + common + </dt> +<dd> + Common code used by the test portlets and the test driver. This + module also contains the XSL stylesheets used during the test + portlet module build to generate the test case list and page + configuration for the module. + </dd> +<dt> + deploy + </dt> +<dd> + The directory <code>deploy/target/deploy-files</code> contains the portlet war + files and the page file to be deployed on the system under test. + </dd> +<dt> + driver + </dt> +<dd> + The maven-based test driver. When this module is built, it + generates a consolidated test case list and page file for the test + cases and pages defined by all test case portlet modules. + </dd> +<dt> + TestModule1 + </dt> +<dd> + Intended to be a sample for writing TCK portlets. + Defines several portlets, each of which is placed on its own page. + </dd> +<dt> + TestModule2 + </dt> +<dd> + Intended to be a sample for writing TCK portlets. + Defines several portlets, all of which are placed on the same + portal page. Some tests produce links that are clicked by the test + driver when the test is run. Some tests set public render + parameters that are used by another test portlet. + </dd> +<dt> + TestModule3 + </dt> +<dd> + Intended to be a sample for writing TCK portlets. + Defines two portlets in separate portlet applications for public + render parameter testing. Both portlets are placed on the same + page. When the test driver clicks a test link in one portlet, the + test results are displayed in the second portlet. + </dd> +<dt> + V2*Tests + </dt> +<dd> + Modules with this naming scheme contain test cases to demostrate + backward compatibilty with the Portlet Specification version 2.0. + Portlets whose class names contain the string "_SIG_" contain + generated code for verifying the method signatures. These portlets + should not be changed by hand. The remaining portlets contain + additional V2 verification code. + </dd> +<dt> + V3*Tests + </dt> +<dd> + Modules with this naming scheme test v3.0 specific funtionality. + </dd> +</dl> +</div> +<div class="section"><h3><a name="The_Page_File"></a>The Page File</h3> +<p> + The page file defines the page names for the TCK and the portlets expected to + be on each page. This is an XML file in the form of a Pluto driver configuration + file. The schema for this file is located in the Pluto project at the following + location: + </p> +<p><code>./pluto/pluto-portal-driver/src/main/resources/pluto-portal-driver-config.xsd</code></p> +<p> + After the TCK has been built, complete page file for the TCK pages is contained + in the following file: + </p> +<p><code>./pluto/portlet-tck_3.0/deploy/target/deploy-files/pluto-portal-driver-config.xml</code></p> +<p> + It is expected that vendors will extract the portlet-to-page mapping information + from the page file in order to create the necessary configuration files for + the portal under test. + </p> +<p> + When creating pages for your system, note that the test driver expects links + to all test case pages to be available. + The test driver searches for the page links by link text, so it is important that + the links have the names defined in the page file. + </p> +</div> +<div class="section"><h3><a name="Building_the_TCK"></a>Building the TCK</h3> +<p> + Building the TCK produces the test portlets, a list of test cases in XML format, + an XML-based page file containing the page configuration expected by the test + cases, and the test driver itself. + </p> +<p> + To build portlet war files that do not contain any special configuration, use + the command: + </p> +<p><code>mvn clean install</code></p> +<p> + To build portlet war files that are configured for deployment on Pluto, use the + command: + </p> +<p><code>mvn clean install -Ppluto</code></p> +<p> + These commands can be executed either from the Pluto project base directory or + from the <code>./pluto/portlet-tck_3.0</code> directory. + </p> +</div> +<div class="section"><h3><a name="Deploying_the_TCK"></a>Deploying the TCK</h3> +<p> + Use the page file which has the default + name of <code>deploy/target/deploy-files/pluto-portal-driver-config.xml</code> to create + pages for your system. + The WAR files in the <code>deploy/target/deploy-files</code> + contain the test portlet code. Deploy these files on your system. + </p> +<p> + If you are testing with Apache Pluto, you can simply copy + the page file into the Pluto <code>webapps/pluto/WEB-INF</code> directory in order to set up the + pages. To deploy the WAR files on Pluto, copy them into the Pluto webapps directory. + </p> +</div> +<div class="section"><h3><a name="Running_the_TCK"></a>Running the TCK</h3> +<p> + Configure the parent POM file <code>./pluto/portlet-tck_3.0/pom.xml</code> to + address your system under test. See the properties section in the pom.xml file. + You can set the host name and port for the system under test, and can + also select the browser to be used by the Selenium WebDriver code. Note, + however, that if you use a browser other than "firefox" or "HTMLUnit" you will + have to download and install additional WebDriver software manually, and you may + need to add additional configuration properties (See the test.browser.webDriver + property in the parent POM). + </p> +<p> + At the time of this writing, the HTMLUnit driver does not support JavaScript + adequately for JSR 362 TCK purposes. You may need to try different drivers to + find the appropriate WebDriver driver for your environment. + </p> +<p> + All TCK tests were successfully executed through the test driver against Pluto + using the ChromeDriver web driver. See the portlet-tck_3.0/POM.xml file for + a configuration example. + </p> +<p> + Run the TCK by switching to the driver subdirectory and execute the command: + </p> +<p><code>mvn test -Prun-tck</code></p> +<p> + If you want to run a subset of the tests, use the "-Dtest.module=" option. The + driver will then only execute those tests whose test case name contains the + specified string. For example, if you want to run the signature verification + tests, use the command: + </p> +<p><code>mvn test -Prun-tck -Dtest.module=SIG</code></p> +<p> + You can also exclude specific tests by placing an exclamation point before the + text to be matched. For example, if you want to exclude the signature verification + tests, use the command: + </p> +<p><code>mvn test -Prun-tck -Dtest.module=!SIG</code></p> +<p> + The 'test.dryrun' flag will cause the test cases to be listed without executing them. + For example, the following command will list all of the test cases whose test + case name contains 'ResourceResponse', but will not execute them: + </p> +<p><code>mvn test -Prun-tck -Dtest.module=ResourceResponse -Dtest.dryrun=true</code></p> +<p> + The test driver will wait for a response for a default time of 3 seconds. If this + value proves to be too short, you can change it in the portlet-tck_3.0/POM.xml + file, or you can specify a timeout value using the 'test-timeout' command line + option. The timeout value is specified in seconds, as follows: + </p> +<p><code>mvn test -Prun-tck -Dtest.module=ResourceResponse -Dtest.timeout=5</code></p> +<p> + The test driver has an ignore list containing test case names that are not + required to pass in order for a portal product to be JSR 362 compliant. The + ignore list is an XML file in properties file format located at: + </p> +<p><code>portlet-tck_3.0/driver/src/main/resources/xml-resources/ignoredTestCases.xml</code></p> +<p> + By default, the test driver will ignore and will not execute all test cases + in the ignore list. If you wish to execute all test cases including those in + the ignore list, set the command line flag 'test.ignore' to false: + </p> +<p><code>mvn test -Prun-tck -Dtest.ignore=false</code></p> +</div> +<div class="section"><h3><a name="Passing_the_TCK"></a>Passing the TCK</h3> +<p> + TCK execution is self-policing. If you are a portal vendor and wish to claim + JSR 362 compatibility for your product, you should be able to demonstrate that + this TCK can be executed against your product with no errors. + </p> +</div> +<div class="section"><h3><a name="Contesting_a_Test_Case"></a>Contesting a Test Case</h3> +<p> + When defining and implementing the TCK test cases, care was taken to assure + proper implementation and to test only required functionality. + </p> +<p> + However, mistakes may have occurred. If you feel that a test case is incorrectly + implemented or is invalid as defined, please proceed as follows. + </p> +<p> + In either case, please open an issue at the Pluto Jira: + </p> +<p><code>https://issues.apache.org/jira/browse/PLUTO/</code></p> +<p> + Prefix the summary with 'TCK:' in order to allow TCK issues to be readily + identified. Please be sure to specify the exact name(s) of the test case(s) in + question. + </p> +<p> + If you feel that the test case was implemented incorrectly, you may correct the + implementation and issue a pull request through github here: + </p> +<p><code>https://github.com/apache/portals-pluto/pulls</code></p> +<p> + If you feel that the test case is invalid as defined, you may update the ignore + list and issue a pull request. + </p> +<p> + If we agree that the test case is invalid or incorrectly implemented, we will + fix it or integrate your fix into the Pluto master and version 3.0 branches. + </p> +</div> </div> </div>
