| |
| Release Notes 2.0 |
|
| |
| JCo 2.0 requires Java JDK 1.2 or higher |
JCo 2.0 requires a Java JDK or JRE of version 1.2 or higher.
Customers who still need JDK 1.1 support have to use JCo 1.1.x.
|
|
| |
| Support for SAP Unicode releases |
|
Support for SAP systems running in Unicode mode has been added.
|
|
| |
| Support for request/response model |
|
In addition to the class JCO.Function, two new classes JCO.Request and JCO.Response have
been added to support the request/response model. See Javadoc for details.
|
|
| |
| Enhanced XML support |
|
XML support has been enhanced. From the request/reponse containers XML documents
can be generated which are in compliance with the SAP Interface Repository.
|
|
| |
| New methods IMetaData.getInternalLength(...) |
The interface IMetaData has been augmented by the methods
IMetaData.getInternalLength(int field_index) and IMetaData.getInternalLength(String field_name).
These return the internal length of a field in bytes.
When being connected to SAP non-Unicode systems the methods getLength(...) and getInternalLength(...) will
return the same value whereas on Unicode systems they will differ for certain data types.
|
|
| |
| New methods JCO.Client.send(..) |
|
In order to support the IDoc add-on package, the methods JCO.Client.send(...) have been added.
These methods will send Intermediate Documents generated by the IDoc package to the SAP system.
|
|
| |
| New constructors in class JCO.Server |
|
Two new constructors JCO.Server(Properties properties, IRepository repository) and
JCO.Server(Properties properties, IServerThread thread, IRepository repository)
have been added.
| |
| |
| Renaming and loading of runtime libraries |
|
In order to avoid name conflicts, the JCo runtime libraries have been renamed.
The Java archive sapjco.jar contains the JCo runtime classes. The operating system-dependent
native runtime library sapjcorfc.dll | libsapjcorfc.so | libsapjcorfc.sl
contains the JNI bridge to the RFC library.
JCo 2.0 loads its native runtime library from the same directory where the sapjco.jar
file resides. If it cannot be found there, JCo will search the native runtime library along the path
defined by the java.library.path system property and finally it will use the Java built-in
mechanism for loading it.
The RFC library librfc32.dll | librfccm.so | librfccm.sl is always
loaded by the operating system depending on the appropriate system-defined path.
|
|
| |
| New version dialog |
JCo's version information can now conveniently be determined by using the command
java -jar {sapjco-install-path}/sapjco.jar
or
java -classpath {sapjco-install-path}/sapjco.jar com.sap.mw.jco.About
in the installation directory. The command will pop up a dialog with the relevant version
information. On non-windowing systems one can get the same information
printed to the console by typing
java -jar {sapjco-install-path}/sapjco.jar -stdout
or
java -classpath {sapjco-install-path}/sapjco.jar com.sap.mw.jco.About
-stdout
|
|
