I was wondering if we should upgrade to 1.3.2 or to their 2.0 beta.
Myabe we could use ODE 1.3.2 in 1.x and ODE 2.0 beta in our 2.x
codestream ? Note that the ODE 2.0 beta would take a day or two at
least, as there has been various SPI changes in the ODE 2.x
codestream.

Thoughts ?

On Tue, May 12, 2009 at 11:38 AM, Raymond Feng <[email protected]> wrote:
> Hi,
>
> Should we consider to upgrade our BPEL integration to the latest ODE
> release?
>
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Alexis Midon" <[email protected]>
> Sent: Tuesday, May 12, 2009 10:08 AM
> To: <[email protected]>
> Subject: [ANNOUNCE] Apache ODE 1.3.2 released
>
>> The Apache ODE community is proud to announce its latest major
>> release: Apache ODE 1.3.2
>>
>> Apache ODE is a WS-BPEL compliant web services orchestration engine.
>> It organizes web services calls following a process description
>> written in the BPEL XML grammar. Another way to describe it would be a
>> web-service capable workflow engine.
>>
>> This new release includes many features and improvements, among others:
>>  . XQuery 1.0 in BPEL queries and expressions
>>  . Publish/Subscribe across process instances
>>  . WS-BPEL processes provided over JMS
>>  . WS-Security support
>>  . Process data cleanup
>>  . better performance and memory management
>>
>> As well as many bug fixes. See the release notes for an exhaustive list:
>> https://issues.apache.org/jira/browse/ODE/fixforversion/12313906
>>
>> For more information, check the Apache ODE website:
>> http://ode.apache.org/getting-ode.html
>>
>> Apache ODE is an open source project released under a
>> business-friendly license (Apache License v2.0), as such we welcome
>> all your help and contributions. To participate and get involved, our
>> mailing lists are the best resources to start from:
>> http://ode.apache.org/mailing-lists.html
>>
>> The Apache ODE Team.
>
>



-- 
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Reply via email to