cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <j...@socialchange.net.au>
Subject Re: [PATCH] build.xml fixes
Date Thu, 29 Nov 2001 12:17:07 GMT
On Mon, Nov 26, 2001 at 10:27:29AM +0100, Carsten Ziegeler wrote:
> Hi Jeff,
> 
> thanks for your patch - I applied it partially, see below.
> 
> Jeff Turner wrote:
> > 
> > Hi,
> > 
> > The attached patch for build.xml does the following:
> > 
> >  - JDK 1.3 and higher includes javax.naming.* in
> >    ${java.home}/lib/rt.jar, so include this jar in the default
> >    classpath.
> This is a very subtle part of cocoon. If you compile cocoon with such
> a section and but it then into your servlet engine as a war file,
> it might be that your web application is not running as the rt.jar
> is not found from cocoon. So the only relyable solution is to put
> the jndi.jar into your lib directory before building cocoon.

So I'm a JDK 1.3 user.. my javax.naming classes are in
${java.home}/lib/rt.jar. Must I copy rt.jar into the lib/ directory? But
then it will be copied to my webapp's WEB-INF/lib directory. I *really*
don't want that, because it will cause all sorts of classloader problems
(aside from being 13mb).

So this leaves me confused. How does *anyone* currently build Cocoon
with JDK 1.3 with JNDI support? The build process ignores $CLASSPATH
(try adding rt.jar and then building; no difference). It looks to me
like modifying build.xml is the only way for 1.3 users to compile with
JNDI support.

Anyway, I've attached patches for the latest 2.0 and 2.1, which make two
changes:
 - add ${java.home}/lib/rt.jar to the default classpath
 - add URLs indicating where to obtain optional jars


--Jeff

> Thanks,
> Carsten

Mime
View raw message