Thank you.

Good explaination on the transactionality. I want some clear explaination in detail with all the other qualifiers where to use and when to use, like above instance..

I haven’t used the Human Tasks API inside of a BPEL before, but it wouldn’t surprise me that the invocation isn’t a part of your global transaction. I guess you’ll need to catch the exception and then call the HT API to delete the instance that was created in error.

i m calling create task of human task manager from a long running process using Invoke (Actual Human Task lookup is inside my Java code. I have to roll back the create task if there is any exception occurs after the create task step in my process.

I did the settings as u mentioned and make the activities in my process as “Participates” in the BPEL. But it is not rolling back the create task. Any idea? Is there any way to achieve this without writing compensation handler?

Please advise.

Thanks!
Jay

Sorry for the late reply, not sure how I missed your comment.

The problem you run into when not using the WebSphere Adapter to do your JDBC calls is that you need to manually map between the DataObject representation of your business data and java objects. If your objects are simple, it’s not an issue. If they’re complicated, you could be setting yourself up to write a lot of very boring mapping code.

I wouldn’t say theres more issues than that. JNDI DataSources are used everywhere in WAS, I don’t see an potential “unsupported” issue in using them should anything go wrong.

I did the same but used some custom JDBC code. Do you know of any extra implication that must be taken into consideration? Thanks.