Alex, Thanks a lot for the info.
Process Versioning There's something that's not clear for me: what happens with running instances? If you just replace process, there'll be unexpected results several times. Human Tasks Yes, I know it, and it's a great project! I'll add a link to Tempo. About roadmap and new releases: this are great news! I think it's really important for a project to publish this, so people stays tunned for things that are expecting. Regards, > Andres, > > Some quick comments and links for further information: > > Process Versioning > http://ode.apache.org/user-guide.html#UserGuide-Versioning > > Human Tasks > Tempo <http://tempo.intalio.org> is driving towards BPEL4People support > with > full Apache Ode integration. > > Transactions > Ode (trunk version, not yet released but relatively stable) supports > atomic > transactions. Our hope is to release version 2.0 (from trunk) this year. > http://ode.apache.org/atomic-scopes-extension-for-bpel.html > > Management APIs > The PM API is also published with the JBI IL as native JBI endpoints. > It's > the same WSDL interface as with Axis2. Some evidence here: > http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X/jbi/src/main/java/org/apache/ode/jbi/OdeContext.java > We also have a management console in progress, and should be part of > version > 1.3 (also planned for this year) > > Roadmap > The roadmap is discussed and updated every year during ApacheCon, which is > next week :) > Outstanding work can also be derived from Jira enhancements. > > alex > > > On Mon, Oct 27, 2008 at 8:01 PM, Andres P. Ferrando > <[EMAIL PROTECTED]>wrote: > >> Hi Sandro, >> >> You can find now the first draft at >> http://www.pruna.com.ar/?articulos/bpel_engines_oss_review/en/index >> I hope to be able to complete the missing parts of the draft this week, >> and then correct all missing or wrong stuff. :) >> >> Regards, >> >> Sandro Reichert wrote: >> > Hi Andrés, >> > >> > I'm interested in your comparison of the engines. Is there a draft >> > already (publicly) available? >> > >> >> The main thing missing in project documentation is dates. This dates >> are >> >> really useful to see project's health (how it's growing), and to know >> >> when to expect new stuff (for example, cluster support). >> >> >> >> Is there also any way to organize the roadmap, so it'll be clearer >> which >> >> things are done, and what's next? >> >> >> >> I couldn't find info about release history or release plan. >> > >> > Dates would be very useful! >> > >> > Cheers, >> > Sandro >> > >> >> -- >> Andrés P. Ferrando >> http://www.pruna.com.ar/ >> > -- Andrés P. Ferrando http://www.pruna.com.ar/
