Win a copy of Secure Financial Transactions with Ansible, Terraform, and OpenSCAP this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

Impact of version change of JDK/SDK

Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hello Friends,

I have a query on the JDK version.

I am working in a core java application where present server is residing on NT. Now it is shifted to Windows 2003. It is an applet which is running on the client's applet viewer, install the jar files from the server and hit the server when ever required. The application needs the Java "SDK 1.3.1_06". Presently it downloads the jar files among them it holds xercies.jar, xercesImpl.jar also.

If I change the version of JDK to 1.4 or higher, do I need to download the xercies.jar, xercesImpl.jar two jar files again? I come to know that If JDK version 1.4 or higher is being used, this 2 jars are optional, since JDK 1.4 includes a built-in JAXP-compliant parser.

Is there anybody who can confirm that?
And what is impact on the change of JDK version on the application existing code? Will it make any impact on the threading?
Please help. Thanks in advance.

Posts: 43024
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, Java 1.4 contains a JAXP-compliant parser. I think it's not Xerces, though, but Crimson. But as long as the code sticks to JAXP functionality, it should work fine.

As for other changes, well, in general the code should continue to run fine. You will need to test that, of course.
Screaming fools! It's nothing more than a tiny ad:
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic