[ 
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.

Reply via email to