Add package import statements

The packages below are useful if your component is implemented using the standard CORBA IDL-to-Java datatype mappings:

Package(s)	Description
org.omg.CORBA	Contains Java holder and helper classes for each of the core CORBA datatypes. Also defines the interfaces for a standard Java client-side Object Request Broker.
com.sybase.CORBA.jdbc11.*	Contains utility classes for converting between EAServer IDL datatypes and core Java datatypes.
com.sybase.jaguar.server	Contains utility classes for use in server-side Java code.
com.sybase.jaguar.sql	Defines interfaces for defining and sending result sets.
com.sybase.jaguar.jcm	Provides the Java Connection Management (JCM) classes.
com.sybase.jaguar.util.JException	Many of the methods in the EAServer Java classes throw JException. Note that the packages com.sybase.jaguar.util and org.omg.CORBA contain identically named classes, so you can not import all classes from both packages. To avoid compilation problems, import JException explicitly or always refer to this class by its full name.

The fragment below shows the import statements for all of these classes:

import org.omg.CORBA.*;
import com.sybase.CORBA.jdbc11.*;
import com.sybase.jaguar.util.JException;
import com.sybase.jaguar.server.*;
import com.sybase.jaguar.sql.*;
import com.sybase.jaguar.jcm.*;