It's a good idea to keep application-level libraries independent of your app
server's system-level libraries. If you put xalan and/or xerces in
$JRUN_HOME/servers/lib, or, even better, $JRUN_HOME/servers/server-name/lib,
there will be no conflict.
Scott Stirling
> -----Original Message-----
> From: Moore, Jim [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 2:28 PM
> To: JRun-Talk
> Subject: RE: xalan and jrun
>
>
> actually i just solved this myself. i had to replace parser.jar
> and jaxp.jar
> in the jrun/lib/ext directory with xerces.jar from apache.
>
> --jim
>
> -----Original Message-----
> From: Moore, Jim [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 1:50 PM
> To: JRun-Talk
> Subject: xalan and jrun
>
>
> Has anyone had any luck getting xalan to work as an xsl processor in jrun?
> anything i try throws the huge errors below. i want to use xalan
> because we
> are not sure that jrun will be used in the live environment, currently we
> are using it only as a dev server, so i don't want to rely on any built-in
> jrun specific functionality.
>
> --jim
>
>
> 500 Internal Server Error
> /foo2.jsp:
>
> javax.servlet.ServletException: Exception thrown on line '10' from page
> 'C:\\Inetpub\\wwwroot\\foo2.jsp'.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
