Featured Posts

java, webservices

Jersey 1.0.2 got released

New version of the reference implementation of JAX-RS 1.0 API got released (sorry for the delayed announce…was busy lately).
Jersey is also integrated in glassfish so will be available in the update center (v2 and v3 when some dependency problems got fixed).

quick start
Paul Sandoz blog

Original blog

bpel, oracle

Oracle BPEL Fault Policy Framework handling custom business faults

From the Oracle forum and from the comments on my article about Oracle BPEL Fault Policy Management i get a lot of questions about how to let the framework handle my own custom defined ‘business faults’.
In certain situations the default set of faults defined by Oracle aren’t suited enough and you need to define your own faults.
If we look into the examples which got supplied by Oracle we can see an example over here. In this example they defined their own NegativeCredit-fault.

The Oracle BPEL Fault Policy Framework by default only handles the faults which are getting returned on an invoke-activity.
So we have our own custom fault and the knowledge we can only let this fault getting catched by the framework by use of an invoke.
So we need atleast for this testscenario 2 bpel processes. One mainprocess which calls a subprocess, and this subprocess will throw the custom business fault.
This fault will get propogated back to the mainprocess and in here we will be able to let the framework handle the fault.


BPEL Processes




Just a simple invoke of the subprocess from the mainprocess. The subprocess with throw a fault, and this fault will be catched in the mainprocess.
throwThe fault to be thrown

From the console start the mainprocess and wait till it comes back with a fault messageinvoke-faultedClick the activity to see the thrown fault

[sourcecode language=’xml’]
[2009/02/13 16:24:41]
“{http://nl.iteye/integration/faults/business}BusinessFault” has been thrown.

Something went wrong!


Ok nice!
So the custom fault we defined in the subprocess reaches the mainprocess.
Now we need to config the fault policy framework so it will get active on our custom business fault.
From the fault we pasted above we need the faultname (BusinessFault) and the namespace (http://nl.iteye/integration/faults/business).

Edit /bpel/domains/default/config/fault-policies/DefaultPolicy.xml and add the next fault :

[sourcecode language=’xml’]


For testing we will just let this fault getting handled by human-intervention.
Now restart the components

opmnctl stopall
opmnctl startall

Now start the mainprocess again and wait till it fails.

invoke-faulted-frameworkIt looks like the framework got active (activity yellow marked) on our custom business fault.

Go to the activities-tab

And click the activity which faulted.

Now we can edit some of the values and let the subprocess get re-invoked.

So, at this moment we’re able to throw our custom business faults and let them getting catched by the framework. Since the fault is only getting catched on the invoke of a partnerlink, we aren’t able to let our custom business fault getting throwned to the process in which we maybe want do something with the data for which we actually throwed the custom business fault. So maybe we want to stay in the subprocess and somehow get the custome business fault thrown inhere, let the framework catch it and update the values of this subprocess with new values an re-execute the subprocess.

The next solution will get this done.
The mainprocess won’t get changed but in the subprocess we will invoke a new process called AllBusinessFaults.

New subprocess 2


The AllBusinessFaults will throw the custom business fault we ‘request’ back on the invoke in this subprocess. Now it wil get catched by the framework and we will be able to change the values of the subprocess instead of the mainprocess.


By using the AllBusinessFaults bpel service like a sort of composite service, we can add the custom business faults in it and throw the one we would like to get thrown. This will work if the collection of custom business faults isn’t that big. I’m sure there will be better solutions for this, but for the scenario i wanted to describe inhere it was good enough for me.

In the examples i provided i don’t use the fault-part of a synchronous invoke to propegate the soap-fault back to the caller, i just throw the fault. The bpel engine itself throws the fault back to the first-level. Whats best practice on this one ?

BPEL Sources (First part of article with mainprocess/subprocess)
BPEL Sources (Second part of article with mainprocess/subprocess/allbusinessfaults)

Oracle BPEL Fault Policy Management

Original blog

esb, open source

Mule IDE 2.0 RC1

I’m currently working on a proof of concept for testing the mule esb for a local goverment.
It’s a nice case to become familiar with a new esb since i mostly did my development on the Oracle ESB/ALSB.
Good too see some differences in concepts/techniques and connectivity and what the open source world has to offer for service busses.
Though the mule-source.org gives me some nice documentation/examples, i was still missing a good ide for development (though most can be done with some simple editor), i still like auto-complete in xml etc.

I already noticed Mule-IDE, but this version wasnt really actively updated, till i noticed a new update on this blog today. Though you can get most work done by running some mule maven archetype and eclipse for the editting of the xml/java, i’m still curious if the ide gives some extra functionality.


Will check it out to see if it’s usefull for my mule development.

Original blog


New blog!

Welcome to my new blog.

Overhere i will try to post once in a while some articles about my knowledge and experience during daily work.

If you would like to see some information on subjects please tell me and i will try to update in the blog.