Nice summary of jBPM failure handling from Angry Bill: jBPM 3.x allows you to define exception handlers in .jpdl. You can define exceptions you want to catch and either recover from the exception, or allow the execution to fail. These exception handlers are incomplete in functionality though. In my last blog, I talked about how asynchronous continuations give you the ability to have guaranteed transitions. If you dive into the asynchronous code though, you see that exception handlers are executed within the same transaction as the command service triggering the node execution. What does this mean? What are the consequences of this?

I have modified the Simple Entity Bean Example (Nov. 2005 - updated) which used mySQL, to use Oracle instead. I have reused most of the stuff and also used the same directory structure.

JBoss on Tuesday said it has added search and data clustering capabilities to its Hibernate Java persistence and object/relational mapping software.

The gist is that Terracotta recently ran ourselves through JBoss's own benchmark for a customer and found that while JBoss was doing 10 - 100 ops per second (depending on the load script used), Terracotta was doing 2000 - 4000. It is worth looking at the webinar to learn about the use case, the customer's architecture under JBoss and their desired architecture goals. The webinar does go into detail on how Terracotta works and perhaps why the performance differences.