Yes, put your servlet in the /WEB-INF/classes directory of your web
application.
<library> is for classes loaded at startup and for use in every application,
these will not get reloaded. (Eg in months and months of using Orion, I've
never once needed a <library> tag)
Mike
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ted Rice
> Sent: Friday, October 27, 2000 12:02 AM
> To: Orion-Interest
> Subject: Servlet Caching Bug?
>
>
> We've experienced what we believe to be
> a bug with Orion in terms of Servlet Caching.
> The situation is detailed here:
>
> 1. We've setup a servlet as a filter for xml, by
> editing orion's global-web-application.xml thusly:
>
> <servlet-chaining servlet-name="XSLPainterServlet"
> mime-type="text/xml"/>
> <servlet>
> <servlet-name>XSLPainterServlet</servlet-name>
>
> <servlet-class>com.apama.xsl.XSLPainterServlet</servlet-class>
> </servlet>
>
>
>
> 2. Additionaly, we've edited orion's application.xml thusly:
> <library path="../../dev/ApplyXSLServlet"/>
>
> and a jar file is placed in this directory containing the
> XSLPainterServlet
> file.
>
>
> We've tested this with an XML file and it works fine.
>
> The problem is when we recompile the class file and rebuild the JAR file
> while
> Orion is running, the new servlet is not used. Orion continues to use the
> old
> servlet in memory.
>
> Is there anyway to hot-redeploy servlets without explicitly restarting
> orion?
>
> Thanks,
>
> Ted Rice
>
>
>
>
