[jira] Updated: (PLUTO-219) element in web.xml files produced by the descriptor/depolyer sub-projects is not valid with respect to the Servlet 2.4 xsd

["Craig Doremus (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/PLUTO-219?page=all ]

Craig Doremus updated PLUTO-219:
--------------------------------

    Fix Version: 1.0.2

> <distributable> element in web.xml files produced by the descriptor/depolyer sub-projects is not valid with respect to the Servlet 2.4 xsd
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: PLUTO-219
>          URL: http://issues.apache.org/jira/browse/PLUTO-219
>      Project: Pluto
>         Type: Bug

>     Versions: 1.0.1
>  Environment: Apache Tomcat 5.5.15
> Servlet 2.4 webapp
>     Reporter: Elliot Metsger
>      Fix For: 1.0.2
>  Attachments: PLUTO-219-01.patch
>
> Perhaps against best practices I have a portlet that puts objects into session attributes that don't implement Serializable.  Normally I prevent warnings from Tomcat by configuring a session manager (a <Manager> element inside a <Context> container) with an empty path name.  See http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html#Standard%20Implementation (look for the pathname attribute).
> However Tomcat (at least v 5.5.15 does) seems to ignore my <Manager pathname=""/> directive when the portlet's web.xml has a "<distributable>" element present.  Tomcat then fires off errors about placing non-serializable objects in the portlet session.
> I think the Pluto descriptors/deployer needs to put the <distributable> element into a web.xml only when its required.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira