aspose file tools*
The moose likes Distributed Java and the fly likes New Java, old CORBA Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "New Java, old CORBA" Watch "New Java, old CORBA" New topic
Author

New Java, old CORBA

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16054
    
  21

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.


Customer surveys are for companies who didn't pay proper attention to begin with.
Nitesh Kant
Bartender

Joined: Feb 25, 2007
Posts: 1638

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.


apigee, a better way to API!
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16054
    
  21

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

Joined: Feb 25, 2007
Posts: 1638

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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: New Java, old CORBA