Technical data

20 BEA WebLogic Integration Release Notes
CR069378
Message Store not found if workflow is rolled back.
CR069442
Multipart input stream does not contain boundary with RosettaNet 1.1
CR069519
Need to be able to export and import WebLogic Integration users and roles.
A command line utility is now available to export and import the following security/user
information: users, roles, organizations, business calendars, and permissions.
CR069633
Optional repeating group is not treated correctly in Format Builder.
CR069883
A SOMSchema validation error occurred.
CR069937
Provide a mechanism for recovery of messages using large message support.
To enable the new large message recovery feature, specify the following option in the
startWeblogic script:
-Dbea.lmsgrecovery=1
CR070036
Rollback path no longer getting invoked.
Workflow exception handling for transactions has been changed for this release. In prior
releases of Weblogic Integration, it was possible for an application exception to cause the
exception handler to execute the rollback actions, even if the transaction was not marked
for rollback only. This would occur if the commit actions included
Exit exception
handler and rollback. This behavior has been corrected in this release.
Now, rollback actions are executed if and only if, when the workflow processor catches a
first-chance exception, the user transaction is found to have been marked for rollback only.
(A first-chance exception is one thrown during normal workflow processing; for example,
from user code or from an EJB. A second-chance exception is one thrown during exception
handler processing.)
CR070231
A conversation named 3A2:1.3 already exists.
To support multiple business protocols (RosettaNet-1.1 and RosettaNet-2.0) for the same
PIP name (e.g., 3A2) and PIP version (for example, 1.3), create separate conversation
definitions with conversation name using PIP name as prefix (for example, 3A2-RN11 and
3A2-RN20) for each business protocol.
CR070251
An interoperability error occurs when using WebLogic Integration and Vitria over
RosettaNet 2.0.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued)
Change Request
Number
Description