Kbase P169459: A static DataSet passed around using JMS API ends up with a different schema than source when receiv
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/07/2010 |
|
Status: Unverified
SYMPTOM(s):
A static DataSet passed around using JMS API ends up with a different schema than source when received back
The same static DatasSet is defined in both sender and receiver
The DataSet is sent through JMS as a dynamic DataSet using the CreateDataSetMessage and SetDataSet APIs
The receiving end reads the DataSet back using the GetDataSet API
The DataSet is received correctly as a dynamic DataSetcorrectly
When trying to pass the received dynamic DataSet to an internal procedure that expects the static Dataset the following errorr are returned:
The caller's temp-table parameter does not match to the target temp-table . (5363)
Parameters for procedure <name> (table <name> and table <name>) do not match. (12311)
FACT(s) (Environment):
OpenEdge 10.2B
All Supported Operating Systems
CAUSE:
Bug# OE00198813
FIX:
As a workaround:
- Use a dynamic DataSet as an input parameter for the internal procedure.
- Then use the WRITE-XML and READ-XML to get the data into the static DataSet. Alternatively use the COPY-DATASET() method.