geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianny Damour <>
Subject Re: <hidden-classes> in jetty-deployer plan.xml
Date Sun, 04 Feb 2007 11:13:00 GMT
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.


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

View raw message