Sorry but I should have looked harder at the stack trace, I have had
similar problems in an OSGi environment from within Muse and just
jumped to the conclusion.

Do any wars work?  If so try and spot the differences as this seems to
be purely a JBoss issue.

Is definitely a classloader type error.  In particular:

>>> org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(
>>> ProfileServiceBootstrap.java:205)
>>>        at
>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
>>> 405)
>>>        at org.jboss.Main.boot(Main.java:209)
>>>        at org.jboss.Main$1.run(Main.java:547)
>>>        at java.lang.Thread.run(Thread.java:595)
>>> Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new
>>> SAX
>>> par
>>> ser
>>>        at
>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBPar
>>> ser.java:97)
>>>        at
>>> org.jboss.xb.binding.UnmarshallerImpl.<init>(UnmarshallerImpl.java:56
>>> )
>>>        at
>>> org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newU
>>> nmarshaller(UnmarshallerFactory.java:96)
>>>        ... 62 more
>>> Caused by: java.lang.ClassCastException:
>>> org.apache.xerces.parsers.XIncludeAware
>>> ParserConfiguration
>>>        at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
>>>        at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
>>>        at
>>> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown
>>> Sou
>>> rce)
>>>        at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)
>>>        at
>>> org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown
>>> Sour
>>> ce)
>>>        at
>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBPar
>>> ser.java:92)
>>>        ... 64 more

this isn't even getting to Muse code and seems to be stuck just on
getting the context configuration read.  Unfortunately I'm not a JBoss
expert (only used it sparingly) but try posting the question on a
JBoss group.

If you do find an answer please reply it to the group, so we can all
benefit.  This unfortunately looks like an unpleasent problem to
solve.

cheers,
Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to