Yeah, I've seen this issue before, and I can't remember what was done
to work around it. But the hidden classes is a good place to start.
Thanks,
Aaron
On 4/7/06, Pablo <[EMAIL PROTECTED]> wrote:
> Paul McMahan wrote:
>
> >Pablo, I think the problem is that your app includes a copy of the
> >commons logging and the server's classloader (which is visible to your
> >app) does too. Try adding this to your deployment plan:
> >
> ><web-app ....>
> > <hidden-classes>
> > <filter>org.apache.commons.logging</filter>
> > </hidden-classes>
> >
> >I'm not sure why deployment didn't fail in jetty, perhaps you would
> >have seen a failure later on when you tried to access your
> >servlets(?).
> >
> >Best wishes,
> >Paul
> >
> >
> I can't see any failure later. Application works fine so there is
> definitely a difference between jetty and tomcat versions.
> I'll try <hidden-classes> trick later.
>
> Thanks
> Pablo
>
