Hi!

Matt Krohn wrote:
> The problem is that ProjectX doesn't support DOM level 2, a requirement for
> me. What would it take to change the internal parser to something that's DOM
> level 2 compliant? Are there currently containers out there that would
> support a level 2 parser? Thanks, Mathew

I guess the EJX classes (which is what uses XML in jBoss) could be
changed to use JAXP, which would make it possible to choose parser more
freely.

/Rickard

> 
> -----Original Message-----
> From: Rickard �berg [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 19, 2000 10:06 AM
> To: jBoss
> Subject: Re: [jBoss-User] jBoss question
> 
> Hi!
> 
> Matt Krohn wrote:
> > I have an EJB running in ejboss that is supposed to use the Xerces XML
> > parser to parse a document. The everything runs fine if I do not invoke
> the
> > parse() method from org.apache.xerces.parsers.DOMParser. I can invoke
> other
> > method without incedent, checking feature settings and whatnot, but
> parse()
> > causes the following error:
> >
> > [server] registered container for ZMLParserService
> > [Bean] Construct ZMLDocument
> > [Bean] About to parse
> > [BeanWrapper] ZMLParserService removing propagation context
> > beanWrapper.invoke(methodInvocation) throwed an exception
> > [Bean] error! java.lang.NoSuchMethodError
> > java.lang.ClassCastException: java.lang.NoSuchMethodError
> >         at
> >
> org.ejboss.invocation.RemoteInvocationHandlerLocalImpl.invoke(RemoteInvocati
> > onHandlerLocalImpl.java:84)
> >         at
> > org.ejboss.container.ProxyContainer.invoke(ProxyContainer.java:192)
> >         at
> >
> org.ejboss.container.ProxyContainerForObject.invoke(ProxyContainerForObject.
> > java:299)
> >         at $Proxy4.parseZMLWebDocumentString(Unknown Source)
> >
> > and so on through the stack.
> >
> > Any idea as to why this is occuring? The parser works fine when run
> locally,
> > and the .jar file for the bean has all the classes the parser requires.
> 
> First of all, you're using EJBoss 1.0 which is not longer being worked
> on. Use at your own risk.
> 
> Second, your choice of parser might conflict with what EJBOss 1.0 uses,
> which is ProjectX. Can you try and use the supplied parser instead? Does
> that remove this problem?
> 
> /Rickard
> 
> >
> > Thanks for any suggestions.
> >
> > Mathew Krohn
> > Zenimax Technology, Inc.
> >
> > [EMAIL PROTECTED]
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> 
> --
> Rickard �berg
> 
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]

-- 
Rickard �berg

@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to