Troubleshooting
Problem
In the Service Data Object in XML Cursor Interface (SDOX) mode, when you use the global elements feature in the business object structure and set BOWrapperBG as the data type in outbound artifacts, then the adapter throws an IllegalArgumentException exception error. This can occur when using a test component during the create, append, overwrite, or retrieve outbound operation.
Symptom
An example of a trace report for the IllegalArgumentException is shown below:
[12/8/09 18:22:00:906 CST] FFDC Exception:java.lang.IllegalArgumentException SourceId:com.ibm.j2ca.flatfile.emd.runtime.FlatFileBaseDataBinding ProbeId:getRecord Reporter:java.lang.Class@61e461e4
java.lang.IllegalArgumentException: Expected a DataObject GlobalElementExample1Wrapper inside GlobalElementExample1WrapperBG but found none.
at com.ibm.j2ca.extension.emd.runtime.internal.DataBindingUtil.getBOFromBG(DataBindingUtil.java:459)
at com.ibm.j2ca.flatfile.emd.runtime.FlatFileBaseDataBinding.getContentObject(FlatFileBaseDataBinding.java:640)
at com.ibm.j2ca.flatfile.emd.runtime.FlatFileBaseDataBinding.getRecord(FlatFileBaseDataBinding.java:118)
at com.ibm.ws.sca.binding.j2c.J2CMethodBindingImpl.invoke(J2CMethodBindingImpl.java:1202)
at com.ibm.ws.sca.binding.j2c.J2CInterfaceBindingImpl.invoke(J2CInterfaceBindingImpl.java:152)
at com.ibm.ws.sca.binding.j2c.handler.J2CImportHandler.invokeDynamicImport(J2CImportHandler.java:1314)
Resolving The Problem
To resolve the problem, you can use either of the following workarounds:
- Use the BOWrapper instead of BOWrapperBG as the data type when you use a component to invoke the outbound operation.
- Call the outbound operations directly from the Java™ code, BPEL (Business Process Execution Language), and other mediation flows.
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21415974