Re: XMLC 2.0.1, Tomcat 4.1.24, Java 1.4.1_01 problem (Tom Hjellming)

David Li <[email protected]>
Newsgroups gmane.comp.java.enhydra.xmlc
Message-ID <[email protected]>
Remove the two jar from TOMCAT_HOME/lib/endorsed. Those two are Java  
API and are in conflicted with XMLC 2.0.1.

Or use XMLC 2.2 Beta 1.

David



>    1.
>
> --__--__--
>
> Message: 1
> Date: Fri, 18 Jul 2003 00:36:50 -0500
> To: [email protected]
> From: Tom Hjellming <[email protected]>
> Subject: Xmlc:  XMLC 2.0.1, Tomcat 4.1.24, Java 1.4.1_01 problem
> Reply-To: [email protected]
>
> I'm trying to migrate my servlet (which uses XMLC 2.0.1 extensively) to
> Tomcat 4.1.24 and Java 1.4.1.
>
> Whenever I try to instantiate a java class generated by XMLC, I get the
> following error:
>
> java.lang.VerifyError:  (class:  
> org/enhydra/xml/lazydom/LazyElementNoNS,
> method: expandAttributes signature: ()V) Incompatible object argument  
> for
> funtion call
>          at java.lang.Class.forName0(Native method)
>          at java.lang.Class.forName(Class.java:140)
>          at
> org.enhydra.xml.lazydom.html.LazyHTMLDocument.populateElementType(LazyH 
> TMLDocument.java:689)
>          at
> org.enhydra.xml.lazydom.html.LazyHTMLDocument.populateElementTypes(Lazy 
> HTMLDocument.java:620)
>          at
> org.enhydra.xml.lazydom.html.LazyHTMLDocument.(LazyHTMLDocument.java:70 
> 1)
>          at
> org.enhydra.xml.xmlc.dom.lazydom.LazyHTMLDomFactory.createDocument(Lazy 
> HTMLDocument.java:46)
>
> I've looked throughout my environment and can not find any other  
> competing
> xmlc.jar file -- or any place along the CLASSPATH where an
> org.enhydra.xml.lazydom.LazyElementNoNS class could be found.
>
> Any ideas?
>
> Thanks in advance,
>
>
> Tom Hjellming
> Full Tilt
>
>
>
> --__--__--
>
> _______________________________________________
> XMLC mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>
>
> End of XMLC Digest
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.