Assembly editor Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
   2.1 WSDL operations with multi-part output not supported in two cases
   2.2 Imports and exports cannot suspend transactions
   2.3 CICS ECI transactions only run in transaction mode
   2.4 A single component cannot have multiple operations with the same name
3.0 Known problems and workarounds

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphere® Integration Developer assembly editor.

2.0 Limitations

2.1 WSDL operations with multi-part output not supported in two cases

The Service Component Architecture (SCA) specification does not support the following uses of WSDL operations with multi-part output:

2.2 Imports and exports cannot suspend transactions

Imports and exports cannot suspend a transaction. If you need to suspend a transaction, add another component as an intermediary and set its qualifier accordingly.  

For example, if you had an export with a JMS binding and a one-way operation, and you had an import with a SOAP/HTTP binding with a one-way operation (to return data), you would need to add an intermediary component, such as a Java component, between the import and export with a one-way operation and set the qualifier of the component.

2.3 CICS ECI transactions only run in transaction mode

Transactions using the CICS ECI resource adapter run only in transaction mode, not non-transaction mode, regardless of the setting of the qualifier. A current runtime limitation causes this restriction.

2.4 A single component cannot have multiple operations with the same name

In WebSphere Integration Developer 6.0.1, you would receive an error when an interface had two or more operations with the same name. In WebSphere Integration Developer 6.0.2, the interface editor does not allow you to have two or more operations with the same name. You cannot have two operations with the same name because at runtime you cannot predict which operation will be called.

Similarly, in the assembly diagram, you can have multiple interfaces on the same component, but none of operations across those interfaces can have the same name. In WebSphere Integration Developer 6.0.1, you would receive a warning that the interface set had overloaded operations, but you could still publish the application. However, you could not predict which operation would be called when two or more operations had the same name. In WebSphere Integration Developer 6.0.2, you will receive an error and will be unable to publish the application.

3.0 Known problems and workarounds

None