I would also consider working on improving our WS-BPEL 2.0 support, there are a few interesting things that we don't do yet:
http://ode.apache.org/ws-bpel-20-specification-compliance.html Things like inlined variable initialization, fromPart and toPart in invoke and receive or being able to send/receive classic variables (instead of message variables) would be pretty cool. Implementing them would give you a good breadth of coverage of the ODE code. Thanks, Matthieu On Mon, Oct 20, 2008 at 3:21 AM, Tammo van Lessen <[EMAIL PROTECTED]>wrote: > Madars, > > thanks for your interest in Ode and especially for your interest in > extending it. > > Regarding the WS-* specifications, ODE is mainly reusing the > functionality provided by axis2. Therefore most of the standards below > come with Ode out-of-the-box, however there might be some interesting > tasks targeting a more seamless integration with Ode (e.g. coordinating > transactions across WS)... > > Regarding the BPEL extensions: > - BPEL4People support is not yet implemented but it somehow on our > roadmap. Implementing it shouldn't be too hard, the most difficult part > is however the task manager and the integration with it (i.e. via WS-HT > or with Singleshot, which is rather RESTful). > - BPEL4Chor is a choreography model and is per definition not > executable. Therefore I don't see how it can be implemented in Ode. > > HTH, > Tammo > > Madars Vitolins wrote: > > Hello! > > > > I am student, new for ode and I have planned for my student's work to > > extend ode, add some new standard support. > > What is current ode status for: > > 1) BPEL4PEOPLE > > 2) BPEL4CHOR > > Is there is there something implemented and how hard it would be for > > person to implement it? > > If these are hard bit's is there anything missing in ode from: > > > > WS Reliability > > WS Reliable Messaging > > WS Addressing > > WS Transaction > > WS Security > > > > and how hard would be these to implement? > > > > Thanks a lot in advance, > > Madars > > >
