Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

incompatibilities in the sun.beans.editors package?

 
Rob MacKay
Ranch Hand
Posts: 35
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have some code that compiles fine under 1.6 but does not under 1.7.

During troubleshooting, I notice that in 1.7, the class sun.beans.editors.BoolEditor is now called BooleanEditor. There are no references to the old class name.

Isn't this a break of backwards compatibility at a rather simple level?

Is this something known to Oracle that may be fixed in the future?

What's the best way to work around this incompatibility?

 
Paul Clapham
Sheriff
Posts: 21107
32
Eclipse IDE Firefox Browser MySQL Database
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I believe that all of your questions (except perhaps the last one) are covered here: Why Developers Should Not Write Programs That Call 'sun' Packages.
 
Rob MacKay
Ranch Hand
Posts: 35
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Paul Clapham wrote:I believe that all of your questions (except perhaps the last one) are covered here: Why Developers Should Not Write Programs That Call 'sun' Packages.


LOL.. unfortunately this isn't code I've written, just code I am using. :(

Of course - the "sun" package name hasn't changed here, just the actual class name.
 
Paul Clapham
Sheriff
Posts: 21107
32
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But the bottom line is... it's still broken and needs to be fixed, right? The workaround appears to be "Run under Java 1.6".
 
Rob MacKay
Ranch Hand
Posts: 35
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Paul Clapham wrote:But the bottom line is... it's still broken and needs to be fixed, right? The workaround appears to be "Run under Java 1.6".


Correct since I doubt it would be a good idea to grab the old classes from the 1.6 rt.jar file and stuff them in a patch.jar and use it in the classpath. :)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic