Note: my last question below is meant to imply that you should _not_ put
Xalan or Xerces in your JDK's ext dir. If you do, then the JVM will load
the jaxp in Xerces first and cause problems.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: Scott Stirling [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 10:52 PM
> To: JRun-Talk
> Subject: RE: xalan and jrun
>
>
> I've done it without problems. Maybe you have to put the
> Apache jars in
> your WEB-INF/lib, but I thought I'd done it in the higher lib dirs.
>
> It may be related to how you are loading/using the classes in
> there. They
> should be being loaded by a different classloader than the
> classloader that
> loads JRun's libraries.
>
> Also, are you sure there are no conflicting jars in your
> JVM's bootpath
> (jre/lib/ext)?
>
> Scott
>
> > -----Original Message-----
> > From: Moore, Jim [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, March 06, 2001 6:25 PM
> > To: JRun-Talk
> > Subject: RE: xalan and jrun
> >
> >
> > keeping them separate would be ideal (it does kind of freak me
> > out to remove
> > jrun installed application jars). when i tried it however,
> i got the same
> > results as putting them all in the same folder together
> (i.e. nothing
> > worked). for some reason it seems that xerces.jar can't be
> in the same
> > classpath as parser.jar and jaxp.jar.
> >
> > --jim
> >
> > -----Original Message-----
> > From: Scott Stirling [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, March 06, 2001 5:53 PM
> > To: JRun-Talk
> > Subject: RE: xalan and jrun
> >
> >
> > 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
