You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2007/11/22 15:40:43 UTC

[jira] Created: (PLUTO-442) Create a Testsuite for JSR-286 features

Create a Testsuite for JSR-286 features
---------------------------------------

                 Key: PLUTO-442
                 URL: https://issues.apache.org/jira/browse/PLUTO-442
             Project: Pluto
          Issue Type: Improvement
          Components: portlets-testsuite
    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
            Reporter: Craig Doremus
             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge


We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).

This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545273 ] 

cdoremus edited comment on PLUTO-442 at 11/25/07 10:24 AM:
----------------------------------------------------------------

Applied pluto-testsuite changes from 1.1-286-trunk-merge to 1.1-286-COMPATIBILITY branch in SVN rev 598004 to allow testing of patches applied to this issue in a working pluto-driver since 1.1-286-trunk-merge is still in the middle of refactoring. The only old code kept in the 1.1-286-COMPATIBILITY branch is the hard coded values in pluto-testsuite/src/main/resources/expectedResults.properties since the Maven 2 build has not been modified in this branch to use variables in this file.

      was (Author: cdoremus):
    Applied changes from 1.1-286-trunk-merge to 1.1-286-COMPATIBILITY branch in SVN rev 598004 to allow testing of patches applied to this issue in a working pluto-driver since 1.1-286-trunk-merge is still in the middle of refactoring. The only old code kept in the 1.1-286-COMPATIBILITY branch is the hard coded values in pluto-testsuite/src/main/resources/expectedResults.properties since the Maven 2 build has not been modified in this branch to use variables in this file.
  
> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by CD...@hannaford.com.

Thank you, Torsten. Please also take a look at the patch that Christian
suggested being appied from PLUTO-444 (filters.271107.patch). There appears
to be a conflict with this patch and the PortletServlet class in the
1.1-286-trunk-merge branch. I tried to manually apply the patch, but I
think I got in wrong causing the problems that I reported last Friday. I'm
not sure if filter.231107.patch in PLUTO-444 needs to be applied before
filters.271107.patch. I didn't do that.

Thank you for patching the taglib classes that cleared up the problems with
the admin portlet. I can finally see the future Pluto 2.0 starting to
emerge from the 1.1-286-trunk-merge branch.
/Craig



                                                                           
             Dettborn                                                      
             <dettborn@minet.u                                             
             ni-jena.de>                                                To 
                                       pluto-dev@portals.apache.org        
             12/12/2007 07:59                                           cc 
             AM                                                            
                                                                   Subject 
                                       Re: [jira] Commented: (PLUTO-442)   
             Please respond to         Create a Testsuite for JSR-286      
             pluto-dev@portals         features                            
                .apache.org                                                
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Craig,

when its ok i will fix it tomorrow.

Torsten
Craig Doremus (JIRA) schrieb:
> [
>
https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550938

> ]
>
> Craig Doremus commented on PLUTO-442:
> -------------------------------------
>
> Applied pluto-portal.patch and
> pluto-testsuite.afewfiltertests.patch locally to
> 1.1-286-trunk-merge branch. This fixes all issues reported here
> https://issues.apache.org/jira/browse/PLUTO-442#action_12550045
> except the last one, but the 286 Test Companion portlet on the JSR
> 286 Tests page errors out with this stack trace:
>
> javax.portlet.PortletException: javax.servlet.ServletException:
> javax.servlet.jsp.JspException: An error occurred while evaluating
> custom action attribute "test" with value "${empty
> renderRequest.publicParameterMap}": An error occurred while getting
> property "publicParameterMap" from an instance of class
> org.apache.pluto.internal.impl.RenderRequestImpl
> (java.lang.UnsupportedOperationException: This method needs to be
> implemented.) at
>
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:185)

>  at
>
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:127)

>  at
>
org.apache.pluto.testsuite.test.jsr286.TestCompanionPortlet.doView(TestCompanionPortlet.java:34)

>  at
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:340) at
> javax.portlet.GenericPortlet.render(GenericPortlet.java:246) at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:234)
>  at
> org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

>  at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)

>  at
>
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:205)

>  at
>
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:107)

>  at
>
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:198)

>  at
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
>  at
>
org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspx_meth_pluto_005fportlet_005f0(portlet_002dskin_jsp.java:101)

>  at
>
org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:76)

>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)

>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

>  at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)

>  at
>
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965)

>  at
>
org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fforEach_005f2(pluto_002ddefault_002dtheme_jsp.java:542)

>  at
>
org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fotherwise_005f0(pluto_002ddefault_002dtheme_jsp.java:430)

>  at
>
org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fchoose_005f0(pluto_002ddefault_002dtheme_jsp.java:290)

>  at
>
org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspService(pluto_002ddefault_002dtheme_jsp.java:150)

>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)

>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

>  at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)

>  at
>
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:184)

>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

>  at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

>  at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)

>  at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)

>  at
>
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)

>  at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

>  at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)

>  at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)

>  at
>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>  at
>
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>  at
>
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)

>  at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)

>  at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)

>  at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)

>  at java.lang.Thread.run(Thread.java:595) Caused by:
> javax.servlet.ServletException: javax.servlet.jsp.JspException: An
> error occurred while evaluating custom action attribute "test" with
> value "${empty renderRequest.publicParameterMap}": An error
> occurred while getting property "publicParameterMap" from an
> instance of class org.apache.pluto.internal.impl.RenderRequestImpl
> (java.lang.UnsupportedOperationException: This method needs to be
> implemented.) at
>
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:846)

>  at
>
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)

>  at
>
org.apache.jsp.jsp.TestCompanionPortlet_jsp._jspService(TestCompanionPortlet_jsp.java:119)

>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)

>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

>  at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)

>  at
>
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)

>  at
>
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:178)

>  ... 65 more
>
>> Create a Testsuite for JSR-286 features
>> ---------------------------------------
>>
>> Key: PLUTO-442 URL:
>> https://issues.apache.org/jira/browse/PLUTO-442 Project: Pluto
>> Issue Type: Improvement Components: portlets-testsuite Affects
>> Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge Reporter:
>> Craig Doremus Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>>
>>
>> Attachments: pluto-portal.patch,
>> pluto-testsuite.afewfiltertests.patch,
>> testsuite-annotations.diff,
>> testsuite-with-phase-annotations.patch
>>
>>
>> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It
>> might be best to create separate portlets for these tests since
>> JSR-286 adds features that facilitate interportlet communication
>> (eventing and public render parameters). This issue is a parent
>> issue with specific tasks linked below it including PLUTO-366,
>> PLUTO-367 and PLUTO-368 .
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHX9tH0Ji0BqEIlIURAkoHAKCHP9/9TBd3iKpDYcbpUT37bEEoKACffJOP
lUoZjfFKatjHIr97D5WdOWw=
=L6r3
-----END PGP SIGNATURE-----

Re: [jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by Dettborn <de...@minet.uni-jena.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi Craig,

when its ok i will fix it tomorrow.

Torsten
Craig Doremus (JIRA) schrieb:
> [
> https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550938
> ]
>
> Craig Doremus commented on PLUTO-442:
> -------------------------------------
>
> Applied pluto-portal.patch and
> pluto-testsuite.afewfiltertests.patch locally to
> 1.1-286-trunk-merge branch. This fixes all issues reported here
> https://issues.apache.org/jira/browse/PLUTO-442#action_12550045
> except the last one, but the 286 Test Companion portlet on the JSR
> 286 Tests page errors out with this stack trace:
>
> javax.portlet.PortletException: javax.servlet.ServletException:
> javax.servlet.jsp.JspException: An error occurred while evaluating
> custom action attribute "test" with value "${empty
> renderRequest.publicParameterMap}": An error occurred while getting
> property "publicParameterMap" from an instance of class
> org.apache.pluto.internal.impl.RenderRequestImpl
> (java.lang.UnsupportedOperationException: This method needs to be
> implemented.) at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:185)
>  at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:127)
>  at
> org.apache.pluto.testsuite.test.jsr286.TestCompanionPortlet.doView(TestCompanionPortlet.java:34)
>  at
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:340) at
> javax.portlet.GenericPortlet.render(GenericPortlet.java:246) at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:234)
>  at
> org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>  at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
>  at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
>  at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
>  at
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:205)
>  at
> org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:107)
>  at
> org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:198)
>  at
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
>  at
> org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspx_meth_pluto_005fportlet_005f0(portlet_002dskin_jsp.java:101)
>  at
> org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:76)
>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>  at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
>  at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
>  at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
>  at
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965)
>  at
> org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fforEach_005f2(pluto_002ddefault_002dtheme_jsp.java:542)
>  at
> org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fotherwise_005f0(pluto_002ddefault_002dtheme_jsp.java:430)
>  at
> org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fchoose_005f0(pluto_002ddefault_002dtheme_jsp.java:290)
>  at
> org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspService(pluto_002ddefault_002dtheme_jsp.java:150)
>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>  at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
>  at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
>  at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>  at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>  at
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:184)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
>  at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>  at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>  at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>  at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>  at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>  at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>  at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>  at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
>  at java.lang.Thread.run(Thread.java:595) Caused by:
> javax.servlet.ServletException: javax.servlet.jsp.JspException: An
> error occurred while evaluating custom action attribute "test" with
> value "${empty renderRequest.publicParameterMap}": An error
> occurred while getting property "publicParameterMap" from an
> instance of class org.apache.pluto.internal.impl.RenderRequestImpl
> (java.lang.UnsupportedOperationException: This method needs to be
> implemented.) at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:846)
>  at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)
>  at
> org.apache.jsp.jsp.TestCompanionPortlet_jsp._jspService(TestCompanionPortlet_jsp.java:119)
>  at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
>  at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>  at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>  at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
>  at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
>  at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
>  at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:178)
>  ... 65 more
>
>> Create a Testsuite for JSR-286 features
>> ---------------------------------------
>>
>> Key: PLUTO-442 URL:
>> https://issues.apache.org/jira/browse/PLUTO-442 Project: Pluto
>> Issue Type: Improvement Components: portlets-testsuite Affects
>> Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge Reporter:
>> Craig Doremus Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>>
>>
>> Attachments: pluto-portal.patch,
>> pluto-testsuite.afewfiltertests.patch,
>> testsuite-annotations.diff,
>> testsuite-with-phase-annotations.patch
>>
>>
>> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It
>> might be best to create separate portlets for these tests since
>> JSR-286 adds features that facilitate interportlet communication
>> (eventing and public render parameters). This issue is a parent
>> issue with specific tasks linked below it including PLUTO-366,
>> PLUTO-367 and PLUTO-368 .
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFHX9tH0Ji0BqEIlIURAkoHAKCHP9/9TBd3iKpDYcbpUT37bEEoKACffJOP
lUoZjfFKatjHIr97D5WdOWw=
=L6r3
-----END PGP SIGNATURE-----

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550938 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied pluto-portal.patch and  pluto-testsuite.afewfiltertests.patch locally to 1.1-286-trunk-merge branch. This fixes all issues reported here https://issues.apache.org/jira/browse/PLUTO-442#action_12550045 except the last one, but the 286 Test Companion portlet on the JSR 286 Tests page errors out with this stack trace:

javax.portlet.PortletException: javax.servlet.ServletException: javax.servlet.jsp.JspException: An error occurred while evaluating custom action attribute "test" with value "${empty renderRequest.publicParameterMap}": An error occurred while getting property "publicParameterMap" from an instance of class org.apache.pluto.internal.impl.RenderRequestImpl (java.lang.UnsupportedOperationException: This method needs to be implemented.)
	at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:185)
	at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:127)
	at org.apache.pluto.testsuite.test.jsr286.TestCompanionPortlet.doView(TestCompanionPortlet.java:34)
	at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:340)
	at javax.portlet.GenericPortlet.render(GenericPortlet.java:246)
	at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:234)
	at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
	at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
	at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
	at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:205)
	at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:107)
	at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:198)
	at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
	at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspx_meth_pluto_005fportlet_005f0(portlet_002dskin_jsp.java:101)
	at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:76)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
	at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
	at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
	at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965)
	at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fforEach_005f2(pluto_002ddefault_002dtheme_jsp.java:542)
	at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fotherwise_005f0(pluto_002ddefault_002dtheme_jsp.java:430)
	at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fchoose_005f0(pluto_002ddefault_002dtheme_jsp.java:290)
	at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspService(pluto_002ddefault_002dtheme_jsp.java:150)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
	at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
	at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
	at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
	at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:184)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
	at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
	at java.lang.Thread.run(Thread.java:595)
Caused by: javax.servlet.ServletException: javax.servlet.jsp.JspException: An error occurred while evaluating custom action attribute "test" with value "${empty renderRequest.publicParameterMap}": An error occurred while getting property "publicParameterMap" from an instance of class org.apache.pluto.internal.impl.RenderRequestImpl (java.lang.UnsupportedOperationException: This method needs to be implemented.)
	at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:846)
	at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)
	at org.apache.jsp.jsp.TestCompanionPortlet_jsp._jspService(TestCompanionPortlet_jsp.java:119)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
	at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
	at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
	at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(PortletRequestDispatcherImpl.java:178)
	... 65 more

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552446 ] 

Christian Raschka commented on PLUTO-442:
-----------------------------------------

Craig,

i think you forgot to add testsuite-286-config.xml.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545422 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied testsuite-with-phase-annotations.patch to 1.1-286-trunk-merge branch in SVN rev 598245. Thank you Ben.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550442 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Fixed checkContextMajorVersion on MiscTest page by modifying javax.portlet.version.major in root pom.xml in SVN rev 603239.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: event_tests.patch

This patch (event_tests.patch) adds two new tests for eventing.  Both pass for the 286-trunk-merge branch.  Also, I added a simple solution for running resource serving tests (the results open in a new window).  Thus, the Resource Filter Test now passes as well.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
>            Reporter: Craig Doremus
>             Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
>         Attachments: event_tests.patch, pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment:     (was: event_tests.patch)

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
>            Reporter: Craig Doremus
>             Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: pluto-testsuite.afewfiltertests.patch

Here are few portlet filter tests, as well as a refactoring of the test suite's portlet.xml to reference the Portlet 2.0 deployment descriptor XSD.  Temporarily its schemaLocation points to the server hosting the latest version of the spec.  Will change this in the future when the XSD is available somewhere else online.  

The portlet filter tests are failing in both the trunk-merge and 286-COMPATIBILITY branches.  Could someone please verify the status of the portlet filter implementations in these branches (i.e., do I have things set up incorrectly, or is the functionality simply not there)?

This patch also provided another that displays the current public render parameters and in the future will keep track of events that are fired for the eventing tests.  This portlet throws an exception right now because RenderRequest.getPublicParameterMap() is unimplemented.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556253#action_12556253 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied event_tests.patch in SVN rev 609168. Thanks Ben!

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
>            Reporter: Craig Doremus
>             Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
>         Attachments: event_tests.patch, pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552472 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Thanks, Christian. testsuite-286-config.xml was added in SVN rev 604932.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: testsuite-annotations.diff

I forgot to add the annotations package to subversion in my local working copy, so they weren't included in my first patch.  Sorry.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550045 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied pluto-portal-driver-impl.urlfix.patch in PLUTO-404 and introduction_jsp.patch sent by Ben Gould to pluto-dev on 12/8/2007. in SVN rev 602887.

The testsuite portlet now works in the 1.1-286-trunk-merge branch, but the following errors occur:

 Page: ExternalAppScopedAttributeTest
 Test: checkSetAppScopedAttributeHereSeenElsewhere
 Message: Click the provided link to validate test.
 
 Page: ExternalAppScopedAttributeTest
 Test: checkSetAppScopedAttributeElsewhereSeenHere
 Message: This test will not pass until you have opened the external resource using the link provided below.

 Page: SessionTimeoutTest
 Test: checkSessionInvalidated
 Message: Click the provided link to validate test.

 Page: MiscTest
 Test: checkContextMajorVersion
 Message: Assertion failed: got major version: 2, expected: 1

 Page: MiscTest
 Test: checkContextServerInfo
 Message: Error invoking checkContextServerInfo (java.lang.reflect.InvocationTargetException): null

>From what I remember, both of the ExternalAppScopedAttributeTest tests do not use a link to confirm the tests.


> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552042 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied pluto-portal.patch and pluto-testsuite.afewfiltertests.patch in SVN revs 604407 and 604408. Fixes all testsuite tests except checkContextServerInfo  (MiscTest), but most 286 tests fail and the 286 Test Companion portlet throws a JSPException as described in previous post. Thank you, Ben, for your hard work on this.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552396 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Commented out broken code in TestCompanionPortlet.jsp (286 Test Companion Portlet) and added text explaining the function of this portlet in SVN rev 604857

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550113 ] 

Christian Raschka commented on PLUTO-442:
-----------------------------------------

There's a patch in Pluto-444 which possible make these tests working, but i havn't tested it yet.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550080 ] 

Benjamin Gould commented on PLUTO-442:
--------------------------------------

There is a bug in the way that the test portlet determines whether or a not a batch of tests fails or passes that cropped up when I added the extra portlet lifecycle phases.  Among other things, the pluto-testsuite.afewfiltertests.patch patch solves this issue.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: pluto-portal.patch

This patch adds the JSR 286 test portlet along with its companion portlet to the default pages of the Pluto portal.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: testsuite-with-phase-annotations.patch

This patch updates the test suite so that JSR 286 test may more easily be written against the testing framework.  This patch adds the following features:

1) Each portlet test can implement a doHeaders() function (default does nothing) that gets called by TestPortlet.doHeaders()

2) Annotations have been added to define the portlet lifecycle phase in which each test method should run.  If a class is not annotated, the default phase is Render.  The @DefaultTestPhase annotation causes all test methods on a PortletTest implementation to be run in the given phase, unless an individual method is annotated with @TestPhase, in which case the default is overriden.

3) Test methods can now have signatures that have specific sub-interfaces of PortletRequest (before, all test methods could only have arguments containing PortletRequest or PortletResponse, rather than RenderRequest, ActionRequest, etc.)  Obviously, the test method signature must agree with the phase denoted by its annotation(s).  For backwards compatibility, test methods can still have signatures containing PortletRequest or PortletResponse.

4) Updated all interfaces and implementations with generics and removed compiler warning related to Java 5 language features.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma resolved PLUTO-442.
-----------------------------

    Resolution: Fixed

Patch was applied long time ago already

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 2.0.0
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 2.0.0
>
>         Attachments: event_tests.patch, pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545420 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied  testsuite-with-phase-annotations.patch to 1.1-286-COMPATIBILITY branch in SVN rev 598238. Thank you Ben.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Gould updated PLUTO-442:
---------------------------------

    Attachment: event_tests.patch

Checked wrong box under "Attachment License", so I'm uploading again.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
>            Reporter: Craig Doremus
>             Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
>         Attachments: event_tests.patch, pluto-portal.patch, pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff, testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PLUTO-442) Create a Testsuite for JSR-286 features

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545273 ] 

Craig Doremus commented on PLUTO-442:
-------------------------------------

Applied changes from 1.1-286-trunk-merge to 1.1-286-COMPATIBILITY branch in SVN rev 598004 to allow testing of patches applied to this issue in a working pluto-driver since 1.1-286-trunk-merge is still in the middle of refactoring. The only old code kept in the 1.1-286-COMPATIBILITY branch is the hard coded values in pluto-testsuite/src/main/resources/expectedResults.properties since the Maven 2 build has not been modified in this branch to use variables in this file.

> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
>                 Key: PLUTO-442
>                 URL: https://issues.apache.org/jira/browse/PLUTO-442
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlets-testsuite
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Craig Doremus
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best to create separate portlets for these tests since JSR-286 adds features that facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including PLUTO-366, PLUTO-367 and PLUTO-368 .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.