Cory,

Could you please get James' help and draft a complete proposal?

Please see 
http://www.google.com/search?hl=en&lr=&safe=off&q=incubator+proposal+site%3Awiki.apache.org&btnG=Search
for a list of proposals, their format and their content.

Once the proposal is ready, please post it to [EMAIL PROTECTED] Also,
please take a peek at the documentation on the
http://incubator.apache.org/ site especially w.r.t to the incubation
process, what to expect and steps involved.

thanks,
dims

On 2/2/06, cory <[EMAIL PROTECTED]> wrote:
> Hi,
>
> BPEL 1.1 is supported.  The code works with Axis 1.3.
>
> Sybase wants this code to be successful within the community and is
> going to work to support it.
>
> Cheers,
>
> -cory
>
> On 2/2/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > Folks,
> >
> > There is no proposal, there is just a zip, unless someone is a
> > clairvoyant, we can't figure out things like. *PLEASE* CC
> > [EMAIL PROTECTED]
> >
> > - Which specific version of the spec is implemented?
> > - Where are the list of known issues?
> > - Where is the TODO list?
> > - Why is Axis version 1.2 RC1 (and not even Axis 1.2 final even if we
> > forget that the current version is Axis 1.3)
> > - Is there any relation to workflow?
> > - Is there no opportunity for interaction with our Existing incubation
> > project Agila?
> > - Are there people from sybase who will be working?
> > - Geronimo is becoming an umbrella rapidly and now ServiceMix wants to
> > be one too?
> > - Why are people talking as though the code is FINAL
> >   (Quoting greg - "there is no need to develope a community around this 
> > code")
> >   (Quoting Rob - "If you've looked at the proposed donated code, this
> > BPEL engine is complete, I can't see any sense in combining it with
> > something else ?" )
> > - Do *ANY* of the existing servicemix committers know this code inside out?
> > - If people are not going to touch this contrib code with a barge pole
> > then why should it be accepted?
> >
> > thanks,
> > dims
> >
> > On 2/2/06, James Strachan <[EMAIL PROTECTED]> wrote:
> > > We have received the generous donation of a complete and working BPE
> > > engine to the ServiceMix project...
> > > http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-dev/
> > > 200602.mbox/%
> > > [EMAIL PROTECTED]
> > >
> > > the contributor has offered to donate to Apache & complete the
> > > necessary software grants & IP clearance and to work with us on
> > > integrating it into ServiceMix.
> > >
> > > For those of you maybe not aware; ServiceMIx is an ESB project
> > > defined around JBI (JSR 208) the JCP standard API to integration
> > > components along with being the standard container model for a BPE.
> > > ServiceMix already has the JBI container and has a suite of JBI
> > > integration components already for smart routing, transformation,
> > > rules, scripting, auditing etc...
> > > http://incubator.apache.org/servicemix/Components
> > >
> > > So it makes complete sense to add a BPE to that component suite. Note
> > > that since ServiceMix already has integration components to Apache
> > > Axis and Apache Tuscany, the integration of the BPE with ServiceMix
> > > should benefit those projects too (with Apache Synapse possibly too
> > > via the Axis integration - though we need to work on that one a bit).
> > >
> > > Also having a BPE fully integrated into Geronimo via the JBI
> > > container would mean that we could start to orchestrate pretty much
> > > everything in the Geronimo stack! I'm certainly very excited by this
> > > move...
> > >
> > >
> > > [ ] +1 accept the donation into the ServiceMix incubator project
> > > [ ] 0  don't mind either way
> > > [ ] -1 I object because: .......
> > >
> > >
> > > Here's my +1
> > >
> > > James
> > > -------
> > > http://radio.weblogs.com/0112098/
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>


--
Davanum Srinivas : http://wso2.com/blogs/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to