Hi Pulasthi, Senaka, Why are we saying "BPEL Integration"? BPEL process is also exposed as a service. So shouldn't this be generic to any service call? From what I see, what you should have is a executor that can do a web service call. The parameters of the service call can be taken from either a G-Reg resource or from the LC configuration or can be passed from the UI it self. I don't see a point in limiting that to only BPEL.
Please correct me if I'm wrong. Thanks, Janaka On Fri, May 31, 2013 at 4:16 PM, Eranda Sooriyabandara <[email protected]>wrote: > Hi Pulasthi, > > Please find the comments inline. > > On Fri, May 31, 2013 at 10:00 AM, Pulasthi Supun <[email protected]>wrote: > >> Hi All >> >> I am working on the $subject. The aim of this feature is make it possible >> to invoke BPEL processes during Lifecycle state transition in G-Reg for >> example with this feature it will be possible to call an BPEL process when >> a "Promote" is done. >> >> This is achieved via a transitions executor and the BPEL process will be >> invoked through an web web-service call. following is an sample Lifecycle >> configuration >> >> <data name="transitionExecution"> >> <execution forEvent="Promote" >> >> class="org.wso2.carbon.governance.registry.extensions.executors.BpelExecutor"> >> <parameter name="bpel.epr" >> value=" >> http://10.200.3.107:9763/services/AdderProcess.AdderProcesshttpAdderProcessBindingEndpoint/"; >> /> >> <parameter name="bpel.payload"> >> <p:AdderProcessRequest xmlns:p="http://wso2.org/bps/sample";> >> <x xmlns="http://wso2.org/bps/sample >> ">/_system/governance/{@resourcePath}/{@xvalue}</x> >> <y xmlns="http://wso2.org/bps/sample >> ">/_system/governance/{@resourcePath}/{@yvalue}</y> >> </p:AdderProcessRequest> >> </parameter> >> </execution> >> </data> >> > > > +1 for this approach. > > > >> >> The transition execution needs to be provided with the following details >> >> >> - End Point Reference of the BPEL >> >> The End point can either be given directly or trough an >> property or artifact attribute >> Ex. <parameter name="bpel.epr" >> value="/_system/governance/{@resourcePath}/{@epr}"/> >> >> - The Payload that needed to invoke the BPEL process. >> >> The values of the payload can be-- >> Nuwan Dias >> >> Member, Management Committee - Solutions Technology Group >> Senior Software Engineer - WSO2, Inc. http://wso2.com >> email : [email protected] >> Phone : +94 777 775 729 defined either directly or trough an property or >> artifact attribute >> Ex. >> <data name="transitionExecution"> >> <execution forEvent="Promote" >> >> class="org.wso2.carbon.governance.registry.extensions.executors.BpelExecutor"> >> <parameter name="bpel.epr" >> value="/_system/governance/{@resourcePath}/{@epr}"/> >> <parameter name="bpel.payload"> >> <p:AdderProcessRequest xmlns:p="http://wso2.org/bps/sample";> >> <x xmlns="http://wso2.org/bps/sample >> ">/_system/governance/{@resourcePath}/{@xvalue}</x> >> <y xmlns="http://wso2.org/bps/sample";>6</y> >> </p:AdderProcessRequest> >> </parameter> >> </execution> >> </data> >> >> - Optional - Define whether the BPEL process to be called in >> an synchronous or asynchronous manner by default synchronous approach is >> used >> >> In the asynchronous mode no response will be saved >> >> - Optional - Define the location to store the response >> - Optional - Define whether the response should be saved as an >> property or artifact attribute >> - Optional - Define the name of the property or attribute to store >> the response >> >> > What you mean by a response of a business process? Can you please give an > example use case for a process sending a response. > > Also if we can go further, we may able to show the current Activity name > executing in the process. When we fully support business process > visualization in G-Reg we may able to use that information for visualizing > the current state of the process instance in G-Reg. > > >> >> >> >> Any feedback and comments are welcome >> >> > thanks > Eranda > > -- > *Eranda Sooriyabandara > *Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > E-mail: eranda AT wso2.com > Mobile: +94 716 472 816 > Linked-In: http://www.linkedin.com/in/erandasooriyabandara > Blog: http://emsooriyabandara.blogspot.com/ > > > > * > * > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Janaka Ranabahu* Member - Solutions Management Committee; Senior Software Engineer; WSO2 Inc.; http://wso2.com* E-mail: [email protected] **M: **+94 718370861** *Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
