Changes in Java 5 API

[Pablo Santa Cruz]

Dear Fellows,

Sorry if it has been discussed earlier but I searched this newsgroup,
java site, and java 5 documentation without luck.

I have been using org.apache.xpath.XPathAPI included in j2sdk1.4
without problems.

Now, I upgraded to java 5 to do some testing and, sadly, this class
now is named:

com.sun.org.apache.xpath.XPathAPI

Does anybody knows the reason of this change?

What other classes have been renamed?

It would be a difficult transition if a lot of class names changed.

Thanks in advance.

 

[xarax]

Dear Fellows,

Sorry if it has been discussed earlier but I searched this newsgroup,
java site, and java 5 documentation without luck.

I have been using org.apache.xpath.XPathAPI included in j2sdk1.4
without problems.

Now, I upgraded to java 5 to do some testing and, sadly, this class
now is named:

com.sun.org.apache.xpath.XPathAPI

Does anybody knows the reason of this change?

What other classes have been renamed?

It would be a difficult transition if a lot of class names changed.

Thanks in advance.

XPath is now a standard part of J2SE 5.0; look
at the JavaDoc for javax.xml.xpath package. The
1.4 support package was renamed to com.sun... to
encourage the transition to the standard package
at javax.xml.xpath.

HTH

 

[Pablo Santa Cruz]

XPath is now a standard part of J2SE 5.0; look
at the JavaDoc for javax.xml.xpath package. The
1.4 support package was renamed to com.sun... to
encourage the transition to the standard package
at javax.xml.xpath.

HTH

Thanks a lot Xarax. It helped. Very much.

Where can I read more about this issue?

The sad part is that I should upgrade all my devel stations (and
probably production stations aswell) to Java 5, or I would have
incompatibilities between classes. Is this right?

Cheers!