You can specify how a Java Open Client maps temp-table parameters at two levels of the interface:

  • At a global level for the AppObject or SubAppObject
  • For each procedure or user-defined function

The settings at each level specify if temp-table parameters are mapped to Java SQL ResultSet or OpenEdge ProDataGraph objects. In projects created with the current release of ProxyGen, all settings indicate that temp-table parameters are mapped by default to ProDataGraph objects. In projects created and maintained in releases prior to OpenEdge Release 10.1A, temp-table parameters are always mapped to SQL ResultSet objects. If you open one of these earlier projects in the current release of ProxyGen, all settings indicate that any temp-table parameters are mapped to SQL ResultSet objects.

However, in any new or existing project that you open in the current release of ProxyGen, if you add a procedure or user-defined function that passes at least one ProDataSet (DATASET or DATASET-HANDLE) parameter, and at least one temp-table (TABLE or TABLE-HANDLE) parameter, the temp-table parameter settings for that procedure or user-defined function indicate that temp-table parameters can only be passed as ProDataGraph objects. This is because the mechanism for accessing temp-table parameters as SQL ResultSet objects is incompatible with the mechanism (ProDataGraph objects) for accessing ProDataSet parameters.

For more information on mapping temp-table parameters to Java SQL ResultSet or OpenEdge ProDataGraph objects, see Java Open Clients.