"kukeltje" wrote : | | "bill.burke(a)jboss.com" wrote : | | Many JBoss.org projects like jBPM have done a great job at being portable to other environments than JBoss AS. Unfortunately, they have not done a great job at taking advantage of the JBoss AS platform and becoming a cohesive suite of projects. Right now, most JBoss.org projects are configured and deployed different and have their own unique, but similar/familiar component models. When you want to use two of these projects together, it becomes painful. | | Correct, so your initiative is really appreciated | Was thinking of integrating Seam bijection/scripting. This might give us some consistency across component/programming models. "kukeltje" wrote : | "bill.burke(a)jboss.com" wrote : | | The thing is, I NEED INPUT from users like yourself. I'm trying to figure out the big picutre. How all these projects at JBoss.org can fit together. Learning how you all use these projects alone or together is part of the process. Please help! | | | | I'm currently looking into jboss esb as well... could be that services running there have to be versioned with process versions.... or not... the late/early binding that jbpm has with subprocesses could be a solution... or not.... ..... lots of challenges in this area.... One of the things I talked to Tom about was adding singleton actions/node/handlers that are created per process definition and had lifecycle equivalent to the startup of the process definition. THis could allow us to define start states which are really connector definitions. Not sure this is a good idea or not. I'll start another thread on it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053702#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...