It is a bad practice to use Sun's proprietary Java classes?

java sun
JARC picture JARC · Dec 2, 2009 · Viewed 16k times · Source

The compiler display warnings if you use Sun's proprietary Java classes. I'm of the opinion that it's generally a bad idea to use these classes. I read this somewhere. However, aside from the warnings are there any fundamental reasons why you should not use them?

Answer

dfa picture dfa · Dec 2, 2009

Because they are internal APIs: they are subject to change in a undocumented or unsupported way and they are bound to a specific JRE/JDK (Sun in your case), limiting portability of your programs.

Try to avoid uses of such APIs, always prefer a public documented and specified class.

Related questions

Where can I find old versions of the JDK and JRE?

To test compatibility, I need to find old versions of the JRE and JDK. Where can I find download links to these files?

Read More
Difference com.sun.jersey and org.glassfish.jersey

What is the difference between com.sun.jersey and org.glassfish.jersey? Currently I have my REST service working on com.sun.jersey and I want to write tests, but I can't find a good tutorial for this (nothing seems …

Read More
How can I suppress java compiler warnings about Sun proprietary API

I'm using the encode() method from the sun.misc.BASE64Encoder package. How do I suppress the compiler warnings that it generates? sun.misc.BASE64Encoder is Sun proprietary API and may be removed in And as a followup, why …

Read More