Hi Senaka,
On Fri, May 31, 2013 at 10:18 AM, Senaka Fernando <[email protected]> wrote: > Hi Pulasithi, > > Looks very good. > > WRT The BPEL epr, it would mostly be a fixed endpoint with a parameterized > host/ip (ex:- https://{@host}:{@port}/services/BPELService. But, > supporting a registry endpoint is also a worthwhile addition. Please add > the the parameterized URL as an example too, so that people will realize > that's possible. > > +1 . will make it clear in the documentation on how parameterization can be used > WRT regards to these, > > - 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 > > Can we use an xpath like syntax to describe where to save the response and > another proper XPath to extract a value from the response? > > Yes we can allow an xpath to be given to extract a value from the response i will add that functionality. but i am not clear on what you meant by " xpath like syntax to describe where to save the response ". Thanks, Pulasthi > Thanks, > Senaka. > > > > 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> >> >> 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 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 >> >> >> Any feedback and comments are welcome >> >> Thanks >> -- >> Pulasthi Supun >> Software Engineer; WSO2 Inc.; http://wso2.com, >> Email: [email protected] >> Mobile: +94 (71) 9258281 >> Blog : http://pulasthisupun.blogspot.com/ >> Git hub profile: https://github.com/pulasthi >> > > > > -- > *Senaka Fernando* > Member - Integration Technologies Management Committee; > Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: [email protected] Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
