[
https://issues.apache.org/jira/browse/PLUTO-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated PLUTO-498:
----------------------------
Component/s: (was: portlet container)
portal driver
Priority: Minor (was: Major)
Fix Version/s: (was: 2.0.0)
unspecified
First of all, this issue is not related to the Pluto portlet container as it
delegates the management and instatiation of portlet fitlers to the managing
portal, which I presume is the portal driver in your case.
As the goal of the portal driver is primarily to serve as testbed for the
container its not a priority nor goal to provide a full blown and every
condition ensured portal environment for it.
For that purpose, you should better look at Jetspeed-2 (which does properly
manage this single instance requirement).
The Pluto *portlet container* fully passes the JSR-286 TCK, as is the latest
Jetspeed 2.2 for that matter.
I'll leave this issue open but adowngrade it to a minor one and without a
determined fix version.
> Portlet Filters initialized and destroyed with each request
> -----------------------------------------------------------
>
> Key: PLUTO-498
> URL: https://issues.apache.org/jira/browse/PLUTO-498
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 2.0.0
> Environment: JDK 1.5.0_16, Tomcat 5.5.27
> Reporter: Brian DeHamer
> Priority: Minor
> Fix For: unspecified
>
>
> Portlet filters appear to be getting initialized and destroyed with each
> incoming request. I expected the filters to work more like servlet filters
> where they are initialized once when the web app starts and then re-used for
> each incoming request. The JSR-286 spec states "Only one instance per
> <filter> declaration in the deployment descriptor is instantiated per Java
> Virtual Machine of the portlet container" (PLT.20.2.1).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
