Thanks Alex,
1. That is very helpful. Is there any expectation as to when the first
release 2.0 release will happen?
2. I see there are 85 jira for 2.0, so that may take a bit?
Some stuff we worked on:
ODE-225 - HowTo: JBoss & ODE - might prob just a link to the RiftSaw
project (https://www.jboss.org/riftsaw)
ODE-41 - CXF Implementation of the IAPI - In RiftSaw we're using the
JBossWS (spi), which allows plugging in CXF and JBossWS Native. I'm
guessing this code will stay in RiftSaw since it will run easiest on
JBoss. We've tried using plain JAXWS but that turned out to be
infeasible. So the spi is the easiest way to support multiple WS stacks.
Thx,
--Kurt
Alex Boisvert wrote:
The trunk has a reworked engine-to-IL contract that supports BART (blocking,
async, reliable, transacted) invokes. The engine part is mostly done; the
IL parts are still a work in progress.
The trunk also supports extension activities and includes support for
Javascript E4X assignments.
Some fixes/improvements that went into 1.X branch still have to be ported to
trunk. We have Jira trackers for these if you want details.
alex
On Tue, Sep 8, 2009 at 10:02 AM, Alexis Midon <[email protected]> wrote:
Hi Kurt,
ODE trunk has two new big features compare to 1.3:
- support for multiple bpel runtimes: ODE 2.0 supports all its previous
runtime verisons so that running process instances are not affected by
upgrades.
- atomic transactions:
http://ode.apache.org/atomic-scopes-extension-for-bpel.html
On the roadmap as well:
- RESTful bpel part 2
- Tuscany integration
anything I'm omitting guys?
Alexis
On Wed, Sep 2, 2009 at 7:26 AM, Kurt T Stam <[email protected]> wrote:
Hi guys,
1. What are currently the differences between the 1.3 branch and the 2.0
branch?
2. When is the expectation there is going to be a release from the 2.0
branch? Any RC being planned?
Thx,
--Kurt
