bpelx:validate Does Not Validate Input

(Doc ID 822529.1)

Last updated on JUNE 10, 2009

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.4.0
This problem can occur on any platform.

Symptoms

You are using bpelx:validate="yes" in an Assign activity so you can validate the input variable and handle validation exceptions, see sample below:

<assign name="assign_name" bpelx:validate="yes">
<copy>
<from>
    <client:s xmlns:client="http://sssss"/>
</from>
<to variable="e_variable" query="/client:s"/>
</copy>
</assign>

In 10.1.3.3.1 MLR#14, when the input value is invalid,  the BPEL process stops and throws the following Invalid xml document exception in the BPEL console.  However in 10.1.3.4 MLR#4, bpelx:validate doesn't validate the variable and the process completes without throwing an exception.

Invalid xml document.
According to the xml schemas, the xml document is invalid. The reason is:
Error::cvc-maxLength-valid: Value '123456789' with length = '9' is not
facet-valid with respect to maxLength '5' for type 'null'.
Error::cvc-type.3.1.3: The value '123456789' of element 'ns1:input' is not
valid.
Please make sure that the xml document is valid against your schemas.




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