To migrate applications that contain CORBA packages:
Use the migration tool with the -gui option to migrate individual CORBA packages, not as part of an application. The CORBA packages are listed separately from the application to which they belong. See “Using migrate with the -gui option”.
Temporarily modify the application to not include the CORBA packages so that the application only contains J2EE entities. Then migrate the application as a J2EE application.
Modify the application using one of these methods:
EAServer Manager – browse to Application | AppName | Packages | PackageName, right-click the appropriate package and select Remove.
jagtool – run:
jagtool remove Package:PackageName Application:AppName
where PackageName is the name of the package and AppName is the name of the application you are removing.
Edit the .properties file – modify the property com.sybase.djc.application.packages, and remove the CORBA package from the list of packages.
After migrating the application to EAServer 6.0, modify it so that it again contains the CORBA packages. Use one of:
Management Console – browse to Application | AppName | Packages. Right-click Packages and select Install Package, then choose the CORBA package that had been removed.
jagtool – run:
jagtool install Package:PackageName Application:AppName
where PackageName is the name of the package and AppName the name of the application you are installing.
Edit the .properties file – modify the property com.sybase.djc.application.packages, and add the CORBA package to the list of packages.
You cannot directly migrate Java CORBA components that
have an implementation class that is not in a package, or manually
create a Java CORBA component in EAServer 6.0 that has an implementation
class that is not in a package.
If you have this situation, move the implementation class into a Java package, and change the component properties to reflect this. That is, modify com.sybase.jaguar.component.java.class.
