Re: jsf/Tomahawk - java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl incompatible with javax.xml.parsers.SAXParserFactory error

That could be caused by providing an alternate version of a library that WAS
already has. Check your class loading behaviour and check the libraries you
have in WEB-INF/lib. There could be some clues there.

--
James R. Perkins


On Tue, Jun 21, 2011 at 08:12, Lim Hock-Chai
<Lim.Hock-Chai@xxxxxxxxxxxxxxx>wrote:

Hello,
I'm encountering a bit of a problem with jsf/tomahawk and hope someone
can point me to the right direction.

In RAD, I've created a new test web project to use jsf and tomahawk to
create a web app. Everything works well.

I then performed that same configuration steps to setup jsf/tomahwak on
the actual (exisitng) web project that I'm supposed to develope my apps
in. When I start the WAS6.1 server, I'm getting the following error in
SystemOut.log:
[6/21/11 9:40:49:332 CDT] 00000016 Digester E
org.apache.commons.digester.Digester getParser Digester.getParser:
java.lang.ClassCastException:
org.apache.xerces.jaxp.SAXParserFactoryImpl incompatible with
javax.xml.parsers.SAXParserFactory


I'm assuming that this is caused by sometype of class conflict between
the existing web app and jsf/tomahawk. My question is does anyone know
how I can find out what jar files is causing this conflict?

Thanks


--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.