Re: xml parser conflicts

[Ted Husted <hu...@apache.org>]

One common conflict can come about when two copies of a JAR are 
available on different segments of a nested classpath. So the question 
here would be whether there is another xerces.jar available to the 
container. There are a number of places where common/shared JARs can be 
loaded.

Since the Digester is open source, a number of IDE's can step down into 
the digester code so you can see exactly where the ClassCastException 
occurs. My favorite is IDEA by IntelliJ.

-Ted.


> Hi Ted:
>  
> I had seen an email exchange between you and Kevin Jones from 
> developmentor regarding XML parser conflicts.  Was there any resolution 
> to this issue?
>  
> I am encountering the same issue on WebSphere 4.0 (on Solaris).  My 
> application uses struts. The xerces.jar is used by both the EJB module 
> and the web module.  Therefore, I bundled the xerces within the ear file 
> at the top level and modified the manifest entries in the web and EJB 
> modules to refer to the xerces.jar.  However, I am getting the 
> ClassCastException for the digestor.  Any thoughts?
>  
> Thanks
> Dayakar
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> The New Yahoo! Search 
> <http://us.rd.yahoo.com/search/mailsig/*http://search.yahoo.com> - 
> Faster. Easier. Bingo.


-- 
Ted Husted,
Struts in Action <http://husted.com/struts/book.html>



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org