SOA 11g: How to Validate / Restrict Output XML Values in BPEL, eg Total Digits for a Decimal Type Field
(Doc ID 1507683.1)
Last updated on MARCH 27, 2020
Applies to:Oracle SOA Suite - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Describe how to restrict / validate the output XML of a BPEL process by way of an example.
A BPEL process is taking an XML message as input and transforms it to an output XML message.
One of the fields in the target XML - std_value - is of type "decimal" with the total number of digits restricted to 12 and fraction digits restricted to 4. If this rule is violated, the transformation should fail.
The definition for the field in the target XML's XSD is as follows:
When testing the corresponding transformation XSLT in JDeveloper with more than 12 digits as input, it is clearly showing it as invalid on the target side. But during runtime, the BPEL does not follow the restriction which leads to an invalid XML generated.
What needs to be done to ensure that the BPEL process follows the restriction?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!