Kelly:
The -- is a known bug in a previous version of xerces. xerces 2.3.0
was released in the last 24 hrs. ad is supposed to cure the problem.
Let me know if it works.
Regards,
Jack Lauman
nwcascades.com
Kelly Chen wrote:
I just wonder if anyone have done this before. I am using JspC
I'm getting the following error in my log files after each webapp is
loaded:
StandardContext[/soap]: Cannot find message associated with key
standardContext.namingInitFailed
I assume this has something to do with JNDI... how can I fix it?
Jack
--
To unsubscribe, e-mail: mailto:[EMAIL
Works fine now thanks!
Jack
Glenn Nielsen wrote:
I ran across that today and committed a change to CVS which
fixes the problem.
Thanks for reporting it.
Glenn
Jack Lauman wrote:
Tomcat 4.x (CVS 12-25-2001) fails to start.
I'm using the following configuration:
RedHat
Tomcat 4.x (CVS 12-25-2001) fails to start.
I'm using the following configuration:
RedHat 7.0 (glibc 2.2.4-18.7.0.3)
jdk1.3.1_02
commons-utils-1.1
commons-collections-1.0
commons-digester-1.1.1
commons-dbcp-20011222
commons-modeler-20011222
commons-pool-20011222
crimson-1.1.3
xerces-1.4.4
I
, and apache had no
problems loading it.
Regards,
Jack Lauman
Craig R. McClanahan wrote:
The autoconf stuff is a total mystery to me, but here's my experience so
far.
Platform: Red Hat Linux 7.1
Problem 1 - Can't find APXS:
I tried ./configure --with-apr=/usr/local --with-apxs
