Re: problem parsing web.xml with

[Stefan Hepper <st...@hursley.ibm.com>]

hi Glenn,
sorry for the late response, I had some holidays :-)
yes we parse also the web.xml as we generate a new web.xml during 
deployment in which we add the J2EE roles defined in the portlet.xml to 
re-use the servlet container role mapping and insert the portlet tag lib 
reference to work around the fact that under J2EE 1.3 there is no search 
for tag libs in the common class loader.

thanks for submitting the patch.

Stefan

Glenn R. Golden wrote:
> It looks like Pluto parses not only portlet.xml but web.xml.  If my 
> web.xml has the following:
> 
> <web-app>
> 
>     <display-name>
>         chef-test
>     </display-name>
> 
>     <!-- the session listener -->
>     <listener>
>         <listener-class>
>             org.chefproject.servlet.SessionListener
>         </listener-class>
>     </listener>
> 
>     <listener>
>         <listener-class>
>             org.chefproject.servlet.AttributeListener
>         </listener-class>
>     </listener>
> 
> I get this error when running:
> 
> 2003-10-29 20:14:47 PortletDefinitionRegistryService initializing...
> 2003-10-29 20:14:50 ServiceManager: An unidentified error occurred
> org.xml.sax.SAXException: unable to find FieldDescriptor for 'listener' 
> in ClassDescriptor of web-app
>         at org.exolab.castor.xml.UnmarshalHandler.startElement(Unknown 
> Source)
> 
> Is this because of an incorrect or incomplete 
> servletdefinitionmapping.xml in pluto?  Has anyone run into this?  
> Anybody know what's missing from this file to let it parse this web.xml?
> 
> Can castor be told to just ignore, not error out, things it doesn't know 
> about?  Anybody know how?
> 
> Thanks.
> 
> - Glenn
> 
>