facebook

org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #225154 Reply

    xsun
    Member

    What operating system and version are you running? win XP
    What Eclipse version and build id are you using? (Help > About Eclipse Platform)Version: 2.1.3
    Build id: 200403101828
    – Was Eclipse freshly installed for MyEclipse? Y
    – If not, was it upgraded to its current version using the update manager?
    – Are any other external plugins installed? P4
    – How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*
    What MyEclipse version are you using? (Help > About Eclipse Platform > Features)Version: 2.7.1
    Build id: 200403241200-2.7.1-GA
    What JDK version are you using to run Eclipse? (java -version)1.4.2_04
    What JDK version are you using to launch your application server?
    What steps did you take that resulted in the issue?
    What application server are you using?
    Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log)

    I am using JBoss3. The changes I made:
    XML Document Builder Factory Class = “org.apache.xerces.jaxp.DocumentBuilderFactoryImpl”
    The default was “org.apache.crimson.jaxp.DocumentBuilderFactoryImpl”.
    SAX Parser Factory Class = “org.apache.xerces.jaxp.SAXParserFactoryImpl”
    The default was “org.apache.crimson.jaxp.SAXParserFactoryImpl”.

    When I start up JBoss server, I got error saying:
    “Caused by: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found”

    I know “org.apache.xerces.jaxp.DocumentBuilderFactoryImpl” is in a xercesImpl.jar file on my machine. So I added that jar file file path to my JBoss3 Paths’ “Append to library path” box, but I still get the same error.

    My colleage doesn’t get this problem. So I think I must be missing something somewhere.

    Thanks!
    xsun

    #225157 Reply

    Riyad Kalla
    Member

    xsun,
    It depends on the version of JBoss you are using, if it is one of the last releases of 3.x series, then use org.apache.xerces, if it is one of the previous releases, then you need to use org.apache.crimson. We were surprised that so late in the release cycle JBoss changed this requirement, we had to change our connector which was a toss up becaue it broke compatibility out-of-the-box with older releases of JBoss 3.

    #225200 Reply

    xsun
    Member

    The JBoss version I am using is 3.2.4 rc1.
    My colleague is using the same.

    I’d like to know how to set runtime class path in MyEclipse. Thanks!

    xsun

    #225207 Reply

    Riyad Kalla
    Member

    I’d like to know how to set runtime class path in MyEclipse.

    Window > Preferences > MyEclipse > Application Servers > JBoss 3 > Paths, you can append/prepend JARs to the classpath here and additionally adjust the library path if you needed to as well.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found

You must be logged in to post in the forum log in