5 Replies Latest reply on Jun 4, 2005 2:03 PM by hritcu

JAXP 1.3 (from JDK 1.5) with JBoss 4

cgeer Apr 20, 2005 12:52 PM

As far as I can tell, JBoss 4 comes with Xerces/Xalan to update the Crimson parser with JDK 1.4.2 to Xerces and make it JAXP 1.2 compliant to meet the J2EE 1.4 specs.

JDK 1.5 comes with Xerces (an adapted Xerces at least) already part of it but also includes the JAXP 1.3 APIs instead of JAXP 1.2. I was able to remove the XML jars from the endorsed directory and run the server with JDK 1.5 but are there any concerns with that I haven't realized yet? Essentially I want to be able to run JBoss 4 with JAXP 1.3 instead of 1.2.

Do newer library versions invalidate the J2EE certification?

Chris

1. Re: JAXP 1.3 (from JDK 1.5) with JBoss 4

hritcu May 18, 2005 8:43 AM (in response to cgeer)

Sorry, I don't have an answer to your concerns, but I found an interesting point in your post:

I was able to remove the XML jars from the endorsed directory and run the server with JDK 1.5 [...]

Could you please explain how did you do that? I tried this too but without success:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878181#3878181
Actions
2. Re: JAXP 1.3 (from JDK 1.5) with JBoss 4

hritcu May 19, 2005 6:51 AM (in response to cgeer)

I tried this too but without success

In the end I managed to make my code work with JAXP 1.3 while JBoss is still using its old (and full of bugs) implementation of Xerces:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878181#3878181

Essentially I want to be able to run JBoss 4 with JAXP 1.3 instead of 1.2

I just did a quick search in the JBoss 4.0.2 source for the phrase "org.apache.xerces" and there are only 11 java source files containing it. That means it wouln't be very hard to make the shift to JAXP 1.3. According to the JAXP 1.3 relese notes the most important incompatibe change in JAXP 1.3 is that the packages for Xerces and Xalan got renamed. This was made on purpose and makes it possible to deliver to the JDK1.4 without using the endorsed standards mechanism. This change lets you reference newer Apache libraries in the classpath, so application developers can use them in the same way that would use any other additions to the Java platform.

As a conclusion, I don't think that moving the implementation of JBoss to JAXP 1.3 will be painless, but this is a necessary evolution.

http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/ReleaseNotes_150.html#changes
http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html#packageNamesWhy
Actions
3. Re: JAXP 1.3 (from JDK 1.5) with JBoss 4

starksm64 Jun 4, 2005 10:47 AM (in response to cgeer)

Any change to the jars used in the j2ee 1.4 certification invalidates the certification. The consequenes are simply that different behavior may be seen, and tests that passed under jaxp1.2 may fail under jaxp1.3. Its your choice to upgrade the xml parser.
Actions
4. Re: JAXP 1.3 (from JDK 1.5) with JBoss 4

mtedone1 Jun 4, 2005 1:03 PM (in response to cgeer)

If I had to use JAXP 1.3 with my application, I would have bundled it with the deployable, rather than changing the server core libraries, unless there are class loading issues.
Actions
5. Re: JAXP 1.3 (from JDK 1.5) with JBoss 4

hritcu Jun 4, 2005 2:03 PM (in response to cgeer)

"mtedone1" wrote:
If I had to use JAXP 1.3 with my application, I would have bundled it with the deployable, rather than changing the server core libraries, unless there are class loading issues.

As long as the server uses the endorsing mechanism I don't know of an elegant way to do this.
You can see a not-so-elegant solution here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878181#3878181
I don't even know if it's ok from the "j2ee 1.4 certification" point of view to replace the endorsing mechanism with plain'ol'jars in the classpath.
But is there a better way?
Actions

Go to original post