<context id="transferCtx" type="Op" parent="myParent" > <refType refId="TransferContextData" /> <refService refid="myJournal" alias="Journal" type="jour" /> </context>
The type definition file includes a definition for the collection:
<type id=" TransferContextData " implClass="com.ibm.dse.base.KeyedCollection" > <KCollDescriptor id="typeDefault" refType="TransferContextData "/> <KCollDescriptor id="FundsTransfer" refType="myFundsTransfer"/> ..... <! Other data elements to be included in the context> </type>
Note that in this case, all of the data within the context is typed data.
You can also define the context in the following way:
<context id="transferCtx" type="Op" parent="myParent" > <refKColl refId="TransferContextData" /> <refService refid="myJournal" alias="Journal" type="jour" /> </context>
In this case, the data definition file contains a definition for the collection:
<kColl id="TransferContextData"> <data id="myFundsTransfer" refType="FundsTransfer"/> <field id="CustomerName"/> .... </kColl>
The second approach enables you to have typed and untyped data in the same context at the same time.