• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

New Java, old CORBA

 
Tim Holloway
Saloon Keeper
Pie
Posts: 18108
51
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've got an app that was written before CORBA was integrated into the JDK (Java 1.18). It uses the Visigenic vbroker CORBA kit, but some of the methods in their org.omg classes didn't make it into standard Java.

What's the easiest way to get this ancient code to operate in a Java 1.5 or 1.6 JVM? I don't have a copy of Visigenics conversion tools.
 
Nitesh Kant
Bartender
Posts: 1638
IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim:
What's the easiest way to get this ancient code to operate in a Java 1.5 or 1.6 JVM?

Will I be wrong in assuming that java 1.5 will be backward compatible with 1.18(There will be a lot of warnings probably, but it must work)

If the package is the same then probably, you have to go with a custom classloader searching its own classpath first before going to the parent.

P.S.: I have not worked on Visigenic vbroker CORBA kit and the above is just considering that it is any other third party library.
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18108
51
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can use compiler source level 1.3 and get by. My problem is that the org.omg classes defined by Sun don't contain some of the methods that the org.omg classes defined by Visigenic do.

Since Java 1.2, the org.omg package has been supplied integral to the JVM, so I'd need to either convert the Visigenic generated code or force an override to the JVM internal packages
 
Nitesh Kant
Bartender
Posts: 1638
IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim:
I'd need to either convert the Visigenic generated code or force an override to the JVM internal packages


I think forcing an override of the JVM internal packages can be done by using a custom class loader. Sometime back i wrote the following:



This classloader if created with selfFirst true, will load the classes using its own classpath first.
It may be of help to you.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic