That was an issue with Hibernate and Spring, that's why it was there. It should be removable as I did it for Tomcat a while back after we found Liferay wasn't working with it in there.
Dain Sundstrom wrote: > Tranql uses antlr, but there may be something else that does (maybe > spring). > > -dain > > On Feb 4, 2007, at 3:13 AM, Gianny Damour wrote: > >> Hi Jarek, >> >> I think the Spring filter is a leftover of the time when the Jetty >> module was used to import Spring to configure WADI. >> >> I do not know why antlr is there. As it is not directly imported by >> Jetty6 poms, I think that we can also drop it. >> >> Thanks, >> Gianny >> >> On 02/02/2007, at 3:07 PM, Jarek Gawor wrote: >> >>> Hi, >>> >>> I have a question about the following entry in the >>> configs/jett6-deployer/src/plan/plan.xml: >>> >>> <hidden-classes> >>> <filter>antlr.</filter> >>> <filter>org.springframework.</filter> >>> </hidden-classes> >>> >>> Is that still needed/necessary? tomcat6-deployer's plan.xml does not >>> have such entry. So is this jetty specific? I believe this is causing >>> problems for me with a WS client code that uses Spring API to >>> configure itself (a WS client gets an automatic dependency on CXF >>> which then has a dependency on the Spring API). >>> >>> Can someone please explain? >>> >>> Thanks, >>> Jarek >>
