[jbossws-dev] [Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

[heiko.braun@jboss.com]

IMO JBPM is the wrong approach. Try to keep it simple and external dependencies to a minimum. RM sequence management is really simple and actually only knows a few conditions. RM source and RM destination just figure out the delta and make the source resubmit the missing messages. 

Looking at the overall picture (like for instance the way a RM destination treats incomplete sequence termination) I agree that it might be regarded as a state machine or could be desinged as such. But IMO this is an implementation detail and JBPM probably adds too much overhead for too little gain. You could probably come up with a simple state machine yourself.    

Regarding the persistence:

I think the only relevant bit to this is the need for a pluggable persistence mechanism. In the beginning some JDBC persistence manager might be sufficient. You may want to take alook at JBossMQ for instance, how they designed it.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026236#4026236

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026236