Hi All, Speaking of advancement, this is pretty interesting too, odd name notwithstanding: https://tendermint.com/
Cheers, Zubin On Fri, Oct 6, 2017 at 12:10 PM, Paul Brown <paulrbr...@gmail.com> wrote: > Hi, Aaron -- > > All sorts of things like that should be on the table, IMHO. The original > design for ODE dates back to 2003 or so, and the state of the art across > the board in middleware has advanced a bit in the last 13 years. > > Cheers. > -- Paul > > > > > On Fri, Oct 6, 2017 at 9:07 AM Aaron Anderson <aander...@apache.org> > wrote: > > > Hi Sathwik, > > Is there any plan to support any other execution languages like > executable > > BPMN 2.0 or SCXML in the future or is the main focus of the project now > > maintaining the current 1.X functionality? Perhaps I should continue to > > research using Ignite for process execution and come back with my > findings. > > Regards, > > Aaron > > > > On Friday, October 6, 2017 1:18 AM, Sathwik B P < > sathwik...@gmail.com> > > wrote: > > > > > > Hi Aaron, > > > > Good to hear from you. > > > > We have added basic clustering capabilities using Hazelcast. JACOB now > uses > > JSON serialization with JACKSON. Both these feature are on the trunk and > > will be coming in 1.4. > > > > We can definitely discuss improving the engine. I am game to make ODE > more > > modular in design, reactive and scalable keeping in mind a migration > path. > > > > regards, > > sathwik > > > > On Fri, Oct 6, 2017 at 3:01 AM, Aaron Anderson <aander...@apache.org> > > wrote: > > > > > Hi Sathwik, > > > I am a dormant Apache ODE committer and I would be interested in > > > contributing to new development on Apache ODE. I attempted to build a > > > prototype several years ago on github (https://github.com/ > > > aaronanderson/ODE-X) but I lost steam building the runtime execution > > > engine. Based on my experience with the 1.X code base there was a large > > > amount of complexity around concurrency, key value storage, and JPA > > > persistence. These issues made clustering challenging if not > impossible. > > > These are the same challenges I tried to overcome with my own runtime > > > engine design. > > > Within the last year I got very excited when I came across the Apache > > > Ignite in memory fabric which can solve all of these scalability > > problems. > > > Recently Ignite introduced built in persistence which would remove the > > > requirement of needing a DB for persistence. Apache Ignite has many > > useful > > > features beyond simple caching such as messaging, flexible transaction > > > management, and of course clustering. It is not difficult to imagine a > > thin > > > business process execution layer on top of Apache Ignite hydrating and > > > dehydrating processes as requests are received and handled. > > > I have my own ideas on building a general purpose virtual process > > > execution runtime leveraging CDI and binary XML but the existing ODE > > JACOB > > > java serialization framework could work just as well with Apache > Ignite. > > If > > > interested I can elaborate on my ideas further. > > > Apache ODE uses antiquated technologies and there is a huge opportunity > > to > > > build a modern Cloud friendly Open Source business process engine > > > exclusively using Apache sponsored technologies. > > > Regards, > > > > > > Aaron > > > > > > > > > > > > > > > > > > On Saturday, September 30, 2017 1:43 AM, Sathwik B P < > > > sathwik...@gmail.com> wrote: > > > > > > > > > Hi Community, > > > > > > Contributions and involvement from the community towards the project's > > > growth over the time has considerably diminished. We are seeking new > > > contributors / committers to continue the growth of the project. > Anybody > > > willing to help the community are welcome. > > > > > > There has been no much feedback post 1.3.7 release from the community. > > > > > > Am working on 1.3.8 release bringing on Java 8, Moving to JPA2 from > JPA 1 > > > (OpenJPA 2.4.2 & Hibernate 4.3.11), Upgrading to Axis2 1.7.6 and > Embedded > > > server on TomEE7.0.4 which is now under release vote. Hope I might be > > able > > > to bring in the 1.3.8 release in the next quater. > > > > > > regards, > > > PMC Chair. > > > > > > > > > > > > > > > > > > >
