----------------------------------------------------------------
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 recently added JSP support to our Servlet hosting plan. We all know JSP
has some serious problems, but people wanted it. ;)
Anyhow, I have run into a little bit of a complication. If a user
includes a bean or imports a class file, it gets complicated. For some
reason, having them include the file in their servlets directory (defined
in their <domain>.zone.properties as a repository) doesn't work. The JSP
code compiles, but in runtime they get ClassNotFound exceptions.
If I give the users a $HOME/classes directory and add this to the
wrapper.classpath in jserv.properties, all works fine.
In general this solution appeals to me because it gives a location for
Java code which doesn't need to reload frequently, as apposed to the
repositories location which uses the custom ClassLoader. The problem is
that I am left wondering if there is any performance hit or scalability
issues with having many wrapper.classpath arguments?
I currently support 30+ VirtualHosts/zones on this box, so I am trying to
find a layout and scheme which makes sense. Any suggestions or feedback
is greatly appreciated. I'll be glad to elaborate on any of these points
if it helps.
Duane Gran
spinweb.net
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
