cory wrote: > What I'm trying to get at is a question to everyone: Will Ode be a > bus? My assumption so far, which could be wrong, is that Ode is not > going to be a bus and would be pretty helpless stand alone.
Our roadmap (http://wiki.apache.org/ode/RoadMap) says that we want to "... avoid introducing any external dependencies to any bus architecture or external protocols so that the core engine can be used by as many external projects as possible while avoiding unnecessary dependencies." I believe our goal with the Integration API (iapi) proposal is to enable integration with a bus (e.g. JBI) or directly to a single transport/binding component (e.g. JMS or SOAP/HTTP), or to a full-blown web service stack (e.g. Axis2), or to a component framework (e.g. SCA). For this to happen, the BPEL engine needs to be aware of MEPs and a few other integration details such as EPR resolution. If there is resemblance to any existing bus framework, it's because there's only so many ways you can abstract web services -- despite many attempts to the contrary ;) When I look at the iapi today, I do not see a way to directly connect Ode to multiple components. That would require a bus implementation to route messages to and from components back to Ode. So based on my understanding of the current iapi proposal, Ode would not be a bus. alex
