UDS formerly Forté 4GL has been EOL’d.
amazingly enough UDS 5.2.4 is still the core part of Sun ONE Integration Server EAI 3.2 that has not been EOL’d as yet.
apparently Sun is still committed to fixing defects but not making any architectural changes to Integration Server EAI.
anyway time to migrate ... where to start from & to where ???
before being merged with/into Sun, Forté was shipping a Java version of Framework classes. according to the Forté documentation
The IIOP-Java mode is different from the IIOP-IDL mode in the following ways:
(a) No IDL file is required because Forte generates all the Java client and server stubs/skeletons classes. This also means, without the intermediate IDL representation, there is little or no lost of datatype mappings between TOOL/Java. The generated classes are dependent on the Forte Java library, $FORTE_ROOT/install/lib/java/forte.zip at both development time and runtime.
(b) Support for object passing-by-value. In the IDL mode, an object cannot be passed - only its reference is passed. Note that object references are still being
used in IIOP-Java mode.
(c) Support for Forte Framework datavalue subclasses. In the IDL mode, the Framework datavalue subclasses were flattened into structs (method-less Java classes). In the Java mode, these datavalue subclasses can be passed by value, appearing as true objects over at the Java end.
(d) Support for TOOL input parameter mode on Forte Framework datavalue subclasses. A Java client passing an input parameter to a TOOL server can expect any changes to be reflected at the client's end.
(e) Support for Unicode strings. In the IDL mode, the vendor's marshalling code truncates Unicode strings (16-bit character-width) into ISO-88591 strings (8-bit character-width). In the Java mode, Forte handles the marshalling with full Unicode support (i.e. no
truncations).
which means some of the Java classes needed to accommodate the transposed Forté code are already available.
but how to get the code transposed ...
No comments:
Post a Comment