Re: Extension activities

Hi Oliver, ODE 2.0 branch was an experimental branch and is not maintained since a very long time. I will have to revisit it myself, in case it involves changes to the ODE object model, then we cannot bring it on any of 1.3.x releases because of chances of breaking binary compatibilities. In

Re: Sources of dependencies

Hi Sathwik, Thank you for your answer. > As of Apache ODE source code distribution, we don't ship any third-party > dependent source along with it nor do we take their source and compile it > ourself. We only use third-party library in it's binary form and it's > binary license will be shipped

Re: Sources of dependencies

Hi Oliver, We make our best effort to list all the third-party licenses. In case something is missing feel free to report them. regards, sathwik On Wed, Oct 18, 2017 at 7:02 PM, Sathwik B P wrote: > Hi Oliver, > > Apache project's source & binaries are under ASLV2. > >

Re: Sources of dependencies

Hi Oliver, Apache project's source & binaries are under ASLV2. Third-party dependent binaries and their licenses will be included in the project distribution. If third-party binary license is not compatible with ASLV2, we don't ship that binary. As of Apache ODE source code distribution, we

Extension activities

Hi, In the context of our usage, we rely on BPEL extension activity support within ODE for enabling the invocation of REST APIs through a corresponding extension bundle. We therefore ported the extension activity support from the 2.0-alpha branch (already some years ago and therefore not up to

Sources of dependencies

Hi, We are going to use Apache ODE in a project with involvement of industry partners. There, we are obliged to proof all (transitive) dependencies ODE uses, in order to guarantee that all of them apply to the Apache License Version 2.0. Unfortunately, we were not able to (automatically)