Re: Tomcat 4.0 Class Loader Reorganization

[Stefano Mazzocchi <st...@apache.org>]

"Craig R. McClanahan" wrote:
> 
> I've changed the way that Tomcat 4.0 loads classes so that we should no
> longer have the "package sealing violation" problems!  It should be
> possible to plug and play any app that has Xerces in its "WEB-INF/lib"
> directory, even if that app also chooses to use JSP pages (which rely on
> the JAXP 1.1 parser, which is causing the package sealing issues).
> 
> I'd appreciate it if you guys would try tonight's nightly build with
> Cocoon and Turbine based apps, and report any problems that you run
> into, so that we can fix them before a "beta 2" release of Tomcat 4.0.

Ok, it works, the "sealing violation" exceptions are gone...

> Craig
> 
> PS:  Stefano, there was also mention in one of your messages about
> problems with "servlet.jar" as well?  Could you fill me in on the
> details if that is still a problem?

... but this problem still remains: Catalina must provide more
reasonable classpath information to the servlet contexts in order for
the webapps to be able to compile parts of itself using javac, like
Cocoon does.

[I previously provided more information to Craig privately]

So, cocoon people, please upgrade to Tomcat-4.0 build 20010218 to avoid
the sealing violation exception.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------

Re: Tomcat 4.0 Class Loader Reorganization

[Berin Loritsch <bl...@apache.org>]

Note there are two CocoonServlets (this may have solved the problem as
well).
The regular one--that works with Tomcat, and the Paranoid one that is
susceptible
to Sealing violations because it separates Cocoon from the Classloader in
the
ServletEngine.

----- Original Message -----
From: Stefano Mazzocchi <st...@apache.org>
To: Craig R. McClanahan <Cr...@eng.sun.com>
Cc: <jo...@apache.org>; Cocoon <co...@xml.apache.org>
Sent: Sunday, February 18, 2001 11:52 AM
Subject: Re: Tomcat 4.0 Class Loader Reorganization


> "Craig R. McClanahan" wrote:
> >
> > I've changed the way that Tomcat 4.0 loads classes so that we should no
> > longer have the "package sealing violation" problems!  It should be
> > possible to plug and play any app that has Xerces in its "WEB-INF/lib"
> > directory, even if that app also chooses to use JSP pages (which rely on
> > the JAXP 1.1 parser, which is causing the package sealing issues).
> >
> > I'd appreciate it if you guys would try tonight's nightly build with
> > Cocoon and Turbine based apps, and report any problems that you run
> > into, so that we can fix them before a "beta 2" release of Tomcat 4.0.
>
> Ok, it works, the "sealing violation" exceptions are gone...
>
> > Craig
> >
> > PS:  Stefano, there was also mention in one of your messages about
> > problems with "servlet.jar" as well?  Could you fill me in on the
> > details if that is still a problem?
>
> ... but this problem still remains: Catalina must provide more
> reasonable classpath information to the servlet contexts in order for
> the webapps to be able to compile parts of itself using javac, like
> Cocoon does.
>
> [I previously provided more information to Craig privately]
>
> So, cocoon people, please upgrade to Tomcat-4.0 build 20010218 to avoid
> the sealing violation exception.
>
> --
> Stefano Mazzocchi      One must still have chaos in oneself to be
>                           able to give birth to a dancing star.
> <st...@apache.org>                             Friedrich Nietzsche
> --------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org