hi Claus, On Fri, 2011-01-07 at 13:14 +0100, Claus Ibsen wrote: > Hi Maceik > > Great work you have done. > > I can see this is also being discussed that the Activiti forum > http://forums.activiti.org/en/viewtopic.php?f=4&t=630 > > From a first impression I would assume the component is best suited > for home at Activiti. > There is a rapid release schedule and I would assume most of the > features and work on the component is more Activiti related than > Camel. After all Camel is just the glue. > > So maybe we should push for it to be donated and included at Activiti, > if they would accept it?
I agree, activiti seems to be better place. > > If not then it can certainly be included out of the box at Apache > Camel. As we love contributions and involvement from the community. > http://camel.apache.org/contributing.html > > For example for the next Camel 2.6 release we got like 8-10 new > artifacts, and only the 2 osgi related was created by a Camel > committer (Guillaume Nodet). So that's a strong sign the community is > kick ass and we love their contributions to Apache Camel. > Yes, from OS projects I'm looking at, Camel seems to be by far most contribution-friendly one - really great attitude :) maciek > > > On Fri, Jan 7, 2011 at 12:26 PM, Maciek Próchniak <m...@touk.pl> wrote: > > Hi, > > > > Activiti (http://activiti.org) is a 'superdelux process engine for > > Java' (quote from http://forums.activiti.org/ ;)), which uses BPMN 2.0 > > and comes with Apache Licence. It has some nice management webapps, and > > can be run either embedded in java application or e.g. in OSGi > > environment. > > > > I wrote simple camel component which enables enables integration with > > activiti. > > You can invoke camel route from process: > > > > <serviceTask id="serviceTask" activiti:delegateExpression="${camel}"/> > > (bpmn 2.0 fragment) > > > > from("activiti:camelProcess:serviceTask") > > .to("log:pl.touk") > > .setBody().property("var1") > > .to("file:///tmp/activiti/serviceTask"); > > > > (camelProcess is name of bpmn process, var1 is variable in process) > > > > You can also signal process from camel route: > > > > <receiveTask id="receive" name="Wait State"/> > > (bpmn 2.0 fragment) > > > > from( "file:///tmp/activiti/receive") > > .convertBodyTo(String.class) > > .setProperty("PROCESS_KEY_PROPERTY").xpath("//@key") > > .to("activiti:camelProcess:receive"); > > (PROCESS_KEY_PROPERTY is business process identifier, camelProcess is > > bpmn process name) > > > > https://github.com/mproch/camel-activiti - here is the code > > https://github.com/mproch/activitiCamelKarafSample - here is sample, > > and here http://forums.activiti.org/en/viewtopic.php?f=4&t=630 is > > description for activiti forum (it starts with some 'why is camel great > > framework ;)). > > > > I'm not sure where does this project really belong to - activiti or > > camel (assuming of course that any community would accept this > > contribution ;)), however activiti is being developing more rapidly now > > (1 month release cycle) so guess it makes more sense to put it in > > activiti. > > > > I'd be grateful for any comments/remarks > > > > br, > > maciek prochniak > > > > > > >
