Why can't you treat an orchestration engine like a component like the way you treat Axis or XFire? Why does the code have to live within ServiceMix? Lot of us want a BPEL engine, we don't want a JBI container. The code coming in does exactly that, it is a BPEL engine and has no relation to JBI or Java for that matter. Why can't you have a separate project for BPEL and add glue code as a JBI component EXACTLY the way you work with other projects like XFire?
Seriously James I've never seen anyone disagree (in any effective manner) with you on the list(s). Why is that? Is it because all decisions happen off-list and all that happens here is the love-fest as Sanjiva described? Community is not about borg-like ok-ing of proposals. We seem to agree on the ends but not on the means. You like a very good integration with a BPEL engine for ServiceMix. I like a very good BPEL engine for its own sake. Am sure we can find people on both sides and some who may like both objectives. Why can't we agree to make it work as a separate entity? If not at least tell us what your *shopping list* contains as to what other JBI components you are going to bring in by the time incubation is over? thanks, dims On 2/3/06, James Strachan <[EMAIL PROTECTED]> wrote: > On 3 Feb 2006, at 13:02, Davanum Srinivas wrote: > > James, > > > > There are 2 problems: > > - As a Geronimo PMC member i feel a BPEL implemenation is out-of-scope > > of what i voted for when i +1'ed incubation for ServiceMix. > > The proposal for ServiceMix clearly says... > http://wiki.apache.org/incubator/ServiceMixProposal > > its a JBI container and component suite. An orchestration engine is a > JBI component so I see this as perfectly within scope. In your vote > you never enumerated what JBI components the ServiceMix project could > and could not develop. Could you maybe give us a list now of what > components you did vote for? > > > > I don't > > like what's happening and the way you are doing it. > > Sorry about that, we're trying to fix it > > > > - Secondly, there just isnt enough information to make a decision one > > way or another. A proposal would clear up things like what the > > "supposed" community thinks about a road map for the future say "BPEL > > 2.0" > > > > So, bottom line, Please draw up a new proposal for a separate project. > > So here's the thing; no-one involved (the folks donating the code and > the committers on the ServiceMix project) want a new project. We all > want to work in the single JBI project, ServiceMix where the JBI > container and JBI components live and are developed, documented and > tested together. We want a single, strong community around JBI. > > James > ------- > http://radio.weblogs.com/0112098/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas : http://wso2.com/blogs/
