Hi Kasun, We are only providing the REST API. This implementation uses the set of underneath Java APIs provided by the Activiti core engine. If we are to provide a single Java API then we have to patch the core engine which is not feasible to do.
Regards, Firzhan -- *Firzhan Naqash* Senior Software Engineer - Integration Platform Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*| blog: http://firzhanblogger.blogspot.com/ <http://firzhanblogger.blogspot.com/> <http://suhothayan.blogspot.com/>* *twitter: https://twitter.com/firzhan007 <https://twitter.com/firzhan007> | linked-in: **https://www.linkedin.com/in/firzhan <https://www.linkedin.com/in/firzhan>* On Sat, Dec 12, 2015 at 6:31 PM, Firzhan Naqash <[email protected]> wrote: > > Hi Philippe, > > I see your point, but I think those cases can (and should, IMO), be > handled by process-specific logic. Since Activiti is a project which has a > very active development team, I´d think many times before adding new > functionality that is WSO2-specific, even if it is not in the core engine - > I´m assuming that the proposed change would be made at the activiti-rest > module. > > > Yeah those cases can be handled by process specific logic or from the > client side. If we are going to handle from the client side, we have to > store all the unique business keys in in-memory/database. But lately this > use cases have become a common one across many enterprise workflow > integration and we decided to add the optional " > skipInstanceCreationIfExist" Boolean flag. Even without using this flag > instance creation will work ( In that case flag is false). > > > Maybe you should post your proposed change in Activiti´s forum and see > what what kind of reation you get from the community. > > +1. I will post it in to the community forum. > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
