IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Limitations, known issues, and workarounds

This section lists the limitations and known issues of this release. It also provides information about any fixes or workarounds that exist for resolving these limitations and issues.

Runtime

Tooling

Processor:

BeanCollection cannot be defined as a child data element of KeyedCollection.

For example, in the following code sample, a BeanCollection is defined as the child element of a Keyed Collection:

Processor definition:
<context id="creditCardsCtx" type="process">
          <refKColl refId="creditCardApplData"/>
</context>
Data definition:
<kColl id="creditCardApplData">
	   <bColl id="creditCardApplDataBean" bean="com.ibm.btt.beancoll.CreditCardApplBean" />
</kColl>
You must revise it as follows:
<context id="creditCardsCtx" type="process">
          <refKColl refId="creditCardApplData"/>
</context>
Data definition:
<bColl id="creditCardApplData" bean="com.ibm.btt.beancoll.CreditCardApplBean" />

Channel

There is a default rule in WebSphere Multichannel Bank Transformation Toolkit channels to define the data formatter and response formatter.

If you do not specify them in the request, WebSphere Multichannel Bank Transformation Toolkit uses csRequestFormat and csReplyFormat configured in operation as data format and response format.

The operation configuration file is as follows:
<QueryStockOp.xml>
<operation id="QueryStockOp" context="stockCtx" 
 	implClass="com.ibm.btt.poc.opstep.QueryStockOp">
	<refFormat name="csRequestFormat" refId="stockFmt" />
	<refFormat name="csReplyFormat" refId="stockFmt" />
</operation>

<fmtDef id="stockFmt">
	<fXML dataName="stockCtxData">
		<fString dataName="code" />
		<fString dataName="price" />
	</fXML>
</fmtDef>
</QueryStockOp.xml>

Trace



Feedback