The following table shows the ABL-to-Java data type mapping for INPUT parameters.

Table 1. ABL-to-Java data type mapping for INPUT parameters
ABL data type Java proxy data type
CHARACTER java.lang.String
COM-HANDLE com.progress.open4gl.COMHandle
DATASET DATASET-HANDLE1 com.progress.open4gl.ProDataGraph
DATE DATETIME DATETIME-TZ java.util.GregorianCalendar
DECIMAL java.math.BigDecimal
HANDLE com.progress.open4gl.Handle
INT64 long
INTEGER int
LOGICAL boolean
LONGCHAR java.lang.String
MEMPTR com.progress.open4gl.Memptr
RAW byte[ ]
RECID long
ROWID com.progress.open4gl.Rowid
TABLE TABLE-HANDLE1 com.progress.open4gl.ProDataGraph

(when mapped as a Java SDO DataGraph)
TABLE TABLE-HANDLE1 java.sql.ResultSet

(when mapped as an SQL ResultSet)1
WIDGET-HANDLE com.progress.open4gl.Handle

The COM-HANDLE, HANDLE, RECID, ROWID, and WIDGET-HANDLE ABL data types are not meaningful outside the OpenEdge environment. Their use is restricted to obtaining the value from an ABL procedure and passing it back to another ABL procedure.

Note: The ABL BUFFER parameter type is not supported in Java Open Clients.
1 ProDataSet (DATASET and DATASET-HANDLE) and temp-table (TABLE and TABLE-HANDLE) parameters require special handling, including the mapping of temp-table fields. For more information on ProDataSet and temp-table parameters, see Pass temp-tables and ProDataSets.