[chubbz327]

i installed myeclipse 2.1 and jboss 3.2.1. jboss starts just fine on its’ own but when i try to launch it from myeclipse it throws the exception listed below:

01:35:05,343 ERROR [Server] Failed to start
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found
at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:495)
at org.jboss.deployment.SARDeployer.init(SARDeployer.java:115)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:694)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:637)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
at org.jboss.Main.boot(Main.java:150)
at org.jboss.Main$1.run(Main.java:388)
at java.lang.Thread.run(Thread.java:479)

[support-michael]

The stack tells you that JBoss is looking for an XMLDocumentBuilderFactory class. Your default JBoss preferences should have provided valid values for this. I just configure Jboss3 for MyEclipse2.6.2 and JDK 1.4.2 using the defaults values provided by the preference store and it spun right up when launched from MyEclipse.

Here are the default settings I used:

Server name = default
XML Document builder factory = org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
SAX parser factory = org.apache.crimson.jaxp.SAXParserFactoryImpl

How did you configure your JBoss3 preferences?

Michael
MyEclipse Support

[chubbz327]

That is exactly how i configured it. The values specifying the “XML Document builder factory ” and “SAX parser factory” were there by default. all i did was add the jboss top directory and enabled the server. All other values i left default.

[support-michael]

Next set of questions:

1) what JDK are you using? It should be a JDK not a JRE?

2) can you look at the JBoss configuration you launch from commandline? Is the JDK you’re using for launching JBoss from commandline the same as that used by the MyEclipse JBoss connector?

Michael

[Scott Anderson]

More Questions:

3) What top level directory are you specifying for JBoss? The class you’re looking for is included in lib/crimson.jar which is automatically included in the JBoss classpath by the JBoss connector so it’s very unusual that it can’t be found.

4) Do you have any XML endorsed directories configured with your JDK configuration? Using a different XML setup than JBoss is expecting may also lead to these types of issues.

–Scott
MyEclipse Support

[R Deleener]

Have exactly the same problem with JBOSS3.2.1

Reason is that crimson.jar isn’t anylonger included in JBoss distribution (where in 3.0(.8) it was)

I’ve solved it by:
1) changing the JBoss3-template (when clicking on JBoss3 in Preferences -MyEclipse):
just replace crimson by xerces
2) still in preferences:
go to path-node and prepend to classpath XercesImpl.jar + xml-apis.jar (both can be found in jboss3.2.1’s lib-directoryundefined

[Author]

Posts