JDeveloper Creating Invalid XML Test Cases When Using Asserts Without a Message (Doc ID 1295871.1)

Last updated on MARCH 31, 2011

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.4 to 10.1.3.5.0 - Release: AS10gR3 to
Information in this document applies to any platform.

Symptoms


In a BPEL process containing a test suite with an Assign. Select the Assign and add a value Assert for one of the variables in the test case and add an expected value, e.g. 1.
Press OK and change to the source view for the test case. The generated XML is incorrect. It is expecting a <message> element, which is not created, e.g.


<assertValue variableName="info" comparisonMethod="string" fatal="true"
patternMatch="false">
<expected>1</expected>
</assertValue>


The expected output is


<assertValue variableName="info" comparisonMethod="string" fatal="true"
patternMatch="false">
<message/>
<expected>1</expected>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms