[jboss-dev-forums] [Design of JBoss ESB] - Re: ESB vs. SOAP community

[mark.little@jboss.com]

There is no need for a separate integration project. JBossSOA is YALI and one too far: JBossESB is the ESB and glue for the other projects that it requires (AS, Drools, jBPM etc.) As Kevin pointed out, governance is happening within a separate project (Overlord) because it does not belong within a single project: it spans them all. SSO is similar.

The last thing we need is another project with associated management and development cycles!

Thomas, if you think there are problems with the way in which JBossESB pulls things together, then call them out. Given the work that the productization folks are doing as well as the ESB team (e.g., http://jira.jboss.com/jira/browse/JBESB-1763) this suggestion for another project seems like a solution looking for a problem.

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

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