|
From: Leif M. <le...@ta...> - 2004-08-27 07:24:11
|
Stefan, Great. I added a mention of this to the docs for the next release as well. Cheers, Leif Pauwels Stefan wrote: >Hi Leif, > >This works fine ! > >Thanks, >Stefan > > >-----Original Message----- >From: wra...@li... >[mailto:wra...@li...] On Behalf Of Leif >Mortenson >Sent: donderdag 26 augustus 2004 14:35 >To: wra...@li... >Subject: Re: [Wrapper-user] System classpath > > >Stefan, >The Wrapper does not directly support the use of the system classpath. Its >use is generally discouraged by most Java users because of all of the >problems that you run into when running multiple applications. There are >times when everything is necessary though. > >Anyway. You should be able to fake the Wrapper into using it by setting your >entire system classpath as a single classpath element. The Wrapper normally >breaks up the classpath into individual jars to make it platform >independent. Because your system classpath will be correct for the current >platform it will work. > >Try the following: >wrapper.classpath.1=%CLASSPATH% > >Let me know how that works. If you have any problems set wrapper.debug=true. >That will let you see the full classpath generated by the Wrapper. > >Cheers, >Leif > > > >Pauwels Stefan wrote: > > > >>Hello, >>I'm running a wrapper service on Solaris. >>My application uses JNDI, and needs JARS that are on the system >>classpath. How can I use the system classpath i.s.o. the >>wrapper.classpath.<n> properties ? Thanks, >>Stefan >> >> |