----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------

Can you modify the invocation of javac to include the desired
classpath?  How "built-in" is it?

Perhaps you can also include the same .jar file in both the
wrapper.classpath and the repository.  It didn't work for Turbine,
though -- the Turbine servlet couldn't load the class.

-- Travis

Kevin MacClay wrote:
> 
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files.  Don't make us guess your problem!!!
> ----------------------------------------------------------------
> 
> I have a class that contains utility functions that I wish to share among
> both servlets and jsp in the same zone.  I'm trying to get this utility
> class to auto-reload so we don't have to restart the server to make an
> update.  So I moved it from the system classpath in jserv.properties to the
> repositories in zone.properties.  This allows it to reload fine.  The
> problem is the JSP files won't compile because when "built-in javac" is run
> on the JSP source, it passes the compiler the classpath settings from
> jserv.properties.  And so the utility class can not be found during
> compilation.  My question is:  Is there a way to have the utility class in
> the classpath for compilation of jsp, but then have it in the repository for
> the interpreter so it can be auto-reloaded?


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search Archives: 
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to