Issue Details (XML | Word | Printable)

Key: PLUTO-219
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Elliot Metsger
Reporter: Elliot Metsger
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pluto

<distributable> element in web.xml files produced by the descriptor/depolyer sub-projects is not valid with respect to the Servlet 2.4 xsd

Created: 01/Mar/06 06:47 AM   Updated: 22/Feb/07 04:58 AM
Return to search
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: unspecified

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works PLUTO-219-01.patch 2006-03-01 10:54 AM Elliot Metsger 11 kB
Environment:
Apache Tomcat 5.5.15
Servlet 2.4 webapp

Resolution Date: 22/Jul/06 05:39 PM


 Description  « Hide
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.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.