anonymous wrote : | There is no such thing as JBossSOA | Exactly - and my point is that there should be a JBossSOA project that has a binary dependency on JBossESB like on any other project that goes into the SOA-P. The benefit is, that JBossESB can have a different lifecycle than JBossSOA, With the current approach JBossESB determines the release cycle, which may be slower than what our community expects of JBossSOA. For example we cannot update JBossWS before JBossESB is ready for the next release. Additionally, all folks that are currently involved in the various SOA projects should become members of JBossSOA. This is important to improve project integration. Thirdly, the JBossESB project should only be concerned with ESB aspects and not try to act as an umbrella project, which it is not. Forthly, component updates and SSO should not be a property of the SOA-P they should be available to the community, develeoped and QAed in JBossSOA. Productisaztion should be the only concern of the SOA-P anonymous wrote : | SOA-P should not touch project code - including the build. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153528#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...