what version xerces are you using in WEB-INF/lib?..(I have 2.8.1.. although
the later distros should parse xsd)
http://www.apache.org/dist/xerces/j/M--
----- Original Message -----
From: <
[hidden email]>
To: "Tomcat Users List" <
[hidden email]>; "Tomcat Users List"
<
[hidden email]>
Cc: "Martin Gainty" <
[hidden email]>
Sent: Wednesday, November 14, 2007 2:15 PM
> Martin,
>
> Thanks for your help. I now get a verbose output on why my context load
> fails: it has to do with the Spring context load listener failing to load
the right XML
> parser to load an XML configuration.
>
> The reason I am posting this to Tomcat's list is this: I have xercesImpl
ver 2.9.0
> in ${CATALINA_BASE}/lib and am using JRE6.0. Yet, the context seems to
fail
> to load the parser. Does this stack trace ring a bell on what the root
cause might be?
>
> If this is irrelevant to Tomcat, pl accept my apologies!
>
> 2007-11-14 11:09:06,371 ERROR [main] context.ContextLoader:205 -
Context initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
validate using XSD: Your JAXP provider
[org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@e3c624] does not support
XML Schema. Are you running on Java 1.4 or below with Apache Crimson?
Upgrade to Apache Xerces (or Java 1.5) for full XSD support.
> at
org.springframework.beans.factory.xml.DefaultDocumentLoader.createDocumentBu
ilderFactory(DefaultDocumentLoader.java:102)
>
>
> Tx,
>
> /Uma
>
> -------------- Original message ----------------------
> From: "Martin Gainty" <
[hidden email]>
> > did you verify your configuration files are proper XML ?
> > which parameter does ContextListener error out on?
> > do you see the message "INFO: ContextListener: contextInitialized()"
> > anywhere in the logs?
> >
> > Log4j.properties has the requisite parameters in and is webapp
accessible
> > when located in /WEB-INF/classes location
> >
http://logging.apache.org/log4j/1.2/manual.html> >
> > ##log4j.properties
> > #identify logfile as receptor of log for root
> > log4j.rootLogger=logfile
> >
> > log4j.appender.logfile=org.apache.log4j.RollingFileAppender
> >
log4j.appender.logfile.File=${CATALINA_HOME}/webapps/YourWebApp/WEB-INF/BigL
> > og.log
> > log4j.appender.logfile.MaxFileSize=512KB
> > # Keep three backup files.
> > log4j.appender.logfile.MaxBackupIndex=3
> > # Pattern to output: date priority [category] - message
> > log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
> > log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n
> >
> >
> > M-
> > ----- Original Message -----
> > From: <
[hidden email]>
> > To: "Tomcat Users List" <
[hidden email]>
> > Sent: Wednesday, November 14, 2007 11:32 AM
> > Subject: Error: ListenerStart
> >
> >
> > >
> > > Environment: Jre6, Tomcat 6.0.14, Linux Redhat
> > >
> > > Is there a Tomcat (6.x) specific way of making ContextListener more
> > verbose
> > > in its "Error: listenerStart" message? I mean is there a log4j setting
for
> > Tomcat
> > > that I can enable to identify why the context load fails?
> > >
> > > Tx,
> > >
> > > /U
> > >
> > > ---------------------------------------------------------------------
> > > To start a new topic, e-mail:
[hidden email]
> > > To unsubscribe, e-mail:
[hidden email]
> > > For additional commands, e-mail:
[hidden email]
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail:
[hidden email]
> > To unsubscribe, e-mail:
[hidden email]
> > For additional commands, e-mail:
[hidden email]
> >
>
>
---------------------------------------------------------------------
To start a new topic, e-mail:
[hidden email]
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]
Locked
