BPEL, retrieving the validate activity fault message by Eric Elzinga
January 27, 2014 Leave a comment
The ‘Validate’ activity in Oracle BPEL gives us the functionality to validate variables again schema definitions.
When using it in your bpel process you will get a nice informative message in the ‘Flow trace’.
When you are using some generic error hospital functionality you also want this message to be available in there.
First try would be, add a Scope around the activity and catch the ‘invalidVariables’ System Fault.
When using a getFaultString on the fault variable or after assigning it to your own fault variable you will see the fault stack will be empty.
Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.


The basic principle behind a Service Oriented Architecture is to orchestrate functional building blocks, primarily web services, in order to achieve a solution which fulfills the given requirements. In order to create a robust solution using Oracle SOA Suite several best practices emerged, one being decoupling web services in order to overcome dependencies during server/composite startup. A general approach for achieving this best practice is to use 
Continuous Delivery is a set of practices, supported by tools and automation, that is focused on answering the question: ‘How much risk is associated with deploying this new change into production?’


ThreadLogic builds upon the popular TDA (Thread Dump Analyzer) by adding logic for common patterns found in application servers. ThreadLogic is able to parse Sun, JRockit, and IBM thread dumps and provide advice based on predefined and externally defined patterns.
