For use in classes that will be run in a JDK-1.0.2-compatible Java virtual machine. Classes in this package use the same names and method syntax as com.sybase.CORBA.jdbc11, except for the following package substitutions:
JDK 1.0.2 package
Most programmers use import statements to determine whether JDK 1.0.2 or JDK 1.1 versions of the classes are used.
For use in classes that will be run in a JDK-1.1-compatible Java virtual machine. Provides classes for converting between EAServer’s predefined IDL datatypes and the core Java language objects:
IDL – Provides methods to convert core Java datatypes to EAServer’s predefined CORBA IDL datatypes.
SQL – Provides methods to convert EAServer’s predefined CORBA IDL datatypes to core Java datatypes.
Classes and interfaces for managing cached JDBC connections in server-side Java code:
jaguar.jcm.JCM class – Provides access to JDBC connection caches that have been defined in EAServer Manager.
jaguar.jcm.JCMCache class – Manages a pool of JDBC connections to a third-tier database server.
jaguar.jcm.JConnectionNotFoundException class – Exception thrown when no connections are available.
Utility classes used in server-side Java code:
jaguar.server.Jaguar class – Provides utility methods for use in server-side Java code.
jaguar.server.JContext class – Instantiates objects that are used to send result sets from a Java component method and provides a method to retrieve rows from a java.sql.ResultSet and forward them to the client.
Interfaces for objects that construct and send row results from a Java server component to the client:
jaguar.sql.JServerResultSet interface – Provides methods to return result rows to a client application. JServerResultSet is similar to the java.sql.ResultSet interface, which is used to retrieve result rows from a server.
jaguar.sql.JServerResultSetMetaData interface – Provides methods for describing the metadata of a result set. Metadata specifies the number of columns in each row as well as the datatype, format, nullability, and so forth for each column.
Utility classes that are used in both server-side and client side Java code:
jaguar.util.JException class – JException is the generic exception that is thrown by methods in the EAServer classes or in generated client stub classes.
jaguar.util.<object>Holder class – Holder classes are used to pass INOUT parameters to component method calls. Each holder class has a value field that contains instances of a specific object or base Java type.
Holder classes for use in code that will run in a version 1.0.2 Java virtual machine:
jaguar.util.jdbc102.<object>Holder class – The com.sybase.jaguar.util.jdbc11 holder classes are used to pass jdbc.sql and jdbc.math objects as INOUT parameters. Use these classes in code that runs in a JDK 1.1 or later virtual machine.
The classes in com.sybase.jaguar.util.jdbc102 and com.sybase.jaguar.util.jdbc11 have identical names and method signatures. You can switch between these classes simply by changing the import statements in your source files.
Holder classes for use in code that will run in a version 1.1 or later Java virtual machine:
jaguar.util.jdbc11.<object>Holder class – The com.sybase.jaguar.util.jdbc11 holder classes are used to pass java.sql and java.math objects as INOUT parameters. Use these classes in code that runs in a JDK 1.1 or later virtual machine.
|Copyright © 2005. Sybase Inc. All rights reserved.|