castor uses a jdbc connection, right ? then why don't you just leverage a single JDBC connection and give that to jbpm and castor. i can't see why would would like to go through all the trouble of trying to implement a new persistence layer on jbpm. i think such tasks are very easy to underestimate and they don't bring value. don't focus too much on simplifying your application architecture. focus on what gives you robust and proven software solutions. your overview schema might become a bit more scattered, but you'll save a heck of a lot of time to go to the beach and the result will be a lot less buggy. that's just my free advice. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054634#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...