Overview

See the iJAG FAQ for instructions on generating Java data object classes for an SAP RFC.

The sap2java open source project provides a developer-friendly API for working with the Open Enterprise Foundation's SAP Java Connector.  This is the code that is executed in the sap2java jar that you will find in your app's WebContent/WEB-INF/lib.

The project also includes a useful tool for the automatic generation of Java data object classes from an SAP remote-enabled function (RFC) interface. 

The iJAG group has modified the sap2java source code to expand its functionality to include handling of more complex RFC interfaces than the original project allowed.   The source code requires occasional enhancement as additional SAP data types not currently accommodated are used by SAP RFC developers.

Generate Java Data Object Classes from an SAP Remote-enabled Function Interface

...

workspace_location ... target project's source code directory (wrapped in double-quotes), e.g., "${workspace_loc}/myproject/src" package_name ... package into which the generated classes will be written, e.g., edu.mit.myproject.proxy rfc_name ... name of the RFC for which Java data object classes will be generated, e.g., Z_UT_MY_RFC

On 17-September-2007, per an iJAG decision, the source code was updated to use the same ABAP-to-Java data type mapping that is used in the SAP NetWeaver 2004s product.  This change comprises version 3.0 of the sap2java project. 

Since this change to the data type mapping affected both the wizard and the code accessed in the sap2java jar within your project's WebContent/WEB-INF/lib they have to be in-sync. This means that if an older OAS project needs to have a proxy regenerated because the interface to the RFC has changed or a new RFC has been created for the project, either the project must be upgraded to the latest version of sap2java or, if that is not practical, the proxies must be generated using the version of sap2java that matches the project's sap2java jar

...

.

Revision History

(latest on top)