Folks, from what I learned last week it seems that ESB is not really the SOA project community edition. Instead we don't seem to have a SOA project for the community. By definition the SOA project would consume other related SOA projects (i.e. messaging, bpm, rules, esb, web services, etc) and bring these technologies together in a meaningful way. Release cycles would be fast and the barrier for community involvement low. It would be the home for integration tests and the umbrella project that everybody is equally involved in. We have JBossAS which gets productized in EAP. In the same way we should have JBossSOA that gets productized into SOAP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153343#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...