Nabble - Apache Ode

tag:old.nabble.com,2006:forum-16254 Nabble - Apache Ode 2009-12-16T21:03:47Z <a href="http://ode.apache.org/" target="_top" rel="nofollow">Ode</a> - Orchestration Director Engine. We are proposing an orchestration service that implements the WSBPEL specification. The implementation will also support Message/Event to process correlation tag:old.nabble.com,2006:post-26823252 RiftSaw-2.0-RC1 Released 2009-12-16T21:03:47Z 2009-12-16T21:03:47Z Kurt T Stam-4 Today we release the first RC of the RiftSaw project. RiftSaw is based <br>on the ODE-1.3.3 release and is optimized for the JBoss Application <br>Server container. Some interesting new features are process deployment <br>in jars, support for any JAX-WS compliant WS stack, UDDI integration and <br>a GWT based console. <br><br>The RiftSaw team would like to thank the ODE developers and the ODE <br>community for their support. <br><br>Cheers, <br><br>--Kurt <br><a href="http://www.jboss.org/riftsaw" target="_top" rel="nofollow">http://www.jboss.org/riftsaw</a><br><br>  <br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26823225 Re: Generating Maven artifacts for ODE 2.0 beta2 2009-12-16T21:00:16Z 2009-12-16T21:00:16Z Alexis Midon well, you could also contribute a nice patch to buildr if you care about <br>dependencies in pom files... <br>I mean that's also how maven started back in the days. <br><br>On Wed, Dec 16, 2009 at 2:27 PM, Daniel Dominguez <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26823225&i=0" target="_top" rel="nofollow">daniel@...</a>>wrote: <br><div class='shrinkable-quote'><br>> Hi Dan, <br>> <br>> I don't know how to solve your buildr issue (or if it's even solvable), but <br>> you might be interested in <a href="http://issues.apache.org/jira/browse/ODE-729" target="_top" rel="nofollow">http://issues.apache.org/jira/browse/ODE-729</a> . <br>>  A small group of us have started preliminary work on "mavenizing" ODE. <br>>  This should definitely solve your problem, but the work has just begun. <br>> <br>> -- <br>> Daniel <br>> <br>> Douglas, Dan wrote: <br>> <br>>> Ok, so I discovered "buildr install..." <br>>> My first brush created the artifacts and put them a local repository.  It <br>>> generated POM files, but there was no dependency info in the files.  Buildr <br>>> knows about the dependencies, is there a way to install the artifacts and <br>>> generate the pom files with the dependency sections? <br>>> <br>>> <br>>> <br>>> On Dec 16, 2009, at 10:14 AM, Douglas, Dan wrote: <br>>> <br>>> So, I'm working on a project and we're building an integration layer <br>>> implementation to front ODE with our own service pipeline.  I want to use <br>>> 2.0 because we plan to use some extensions.  Our builds are Maven-based and <br>>> I'd really like to pull in ODE via dependencies in our POM files, but it <br>>> looks like the 2.0 libraries haven't been published to a repo anywhere (at <br>>> least that I can find... I found the 1.3.3 ones). <br>>> <br>>> I've downloaded the 2.0-beta2 source and I've been able to build it with <br>>> buildr.  I've also generated the eclipse project files.  That got me to <br>>> thinking, is there some undocumented buildr incantation that generates the <br>>> appropriate pom.xml files?  Is 2.0-beta2 published somewhere in a Maven <br>>> repo? <br>>> <br>>> I'd like to get our local repo setup and was hoping to avoid having to do <br>>> the tooling or conversion by hand. <br>>> <br>>> Dan <br>>> <br>>> <br>>> <br>>> <br>> <br></div><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26823138 [jira] Updated: (ODE-735) In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. 2009-12-16T20:46:20Z 2009-12-16T20:46:20Z JIRA jira@apache.org <br>     [ <a href="https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ] <br><br>Tammo van Lessen updated ODE-735: <br>--------------------------------- <br><br>    Fix Version/s:     (was: 1.3.3) <br>                   1.3.4 <br><br>1.3.3 is already released, thus we can't fix it for 1.3.3 but for 1.3.4 <br><br>How did you build the jar files? With Eclipse or with buildr? You will need to use the build system (buildr) to create working jar files. <br><div class='shrinkable-quote'><br>> In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. <br>> --------------------------------------------------------------------------------------------------------------------------------------------------- <br>> <br>>                 Key: ODE-735 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-735" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735</a><br>>             Project: ODE <br>>          Issue Type: Bug <br>>          Components: BPEL Runtime <br>>    Affects Versions: 1.3.3 <br>>         Environment: Tomcat 5.5, Apache ODE 1.3.3 <br>>            Reporter: Ma.Liang <br>>             Fix For: 1.3.4 <br>> <br>>         Attachments: ODE-735.patch <br>> <br>> <br>> I replace the jar with source code, then an error will generate, when starting ODE server, I think the source code do not  match the jars which are in the war. <br>> Exception: <br>> HashMap is not an interface.(Occur in the ProcessStoreImpl.java) </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26822186 [jira] Commented: (ODE-735) In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. 2009-12-16T18:32:18Z 2009-12-16T18:32:18Z JIRA jira@apache.org <br>    [ <a href="https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791746#action_12791746" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791746#action_12791746</a> ] <br><br>Ma.Liang commented on ODE-735: <br>------------------------------ <br><br>The test step is: <br>1: I downloaded the apache-ode-war-1.3.3.war、apache-ode-sources-1.3.3.rar from <a href="http://ode.apache.org/getting-ode.html" target="_top" rel="nofollow">http://ode.apache.org/getting-ode.html</a>. <br>2: I put the ode.war into %Tomcat_home%/webapp/ , then start tomcat, ode engine run normally. <br>3: I import the sources into eclipse and resolve the compiler error. <br>4. New Web Project, named "ode", replace the jars with the source code, copy the responding files in the ode.war into ode project. <br>5. Deploy the ode project into tomcat server , then start the tomcat . <br>6. The error about the JPA persistence generate, such as : <br>    java.util.HashMap is not a interface. <br><br><div class='shrinkable-quote'><br>> In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. <br>> --------------------------------------------------------------------------------------------------------------------------------------------------- <br>> <br>>                 Key: ODE-735 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-735" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735</a><br>>             Project: ODE <br>>          Issue Type: Bug <br>>          Components: BPEL Runtime <br>>    Affects Versions: 1.3.3 <br>>         Environment: Tomcat 5.5, Apache ODE 1.3.3 <br>>            Reporter: Ma.Liang <br>>             Fix For: 1.3.3 <br>> <br>>         Attachments: ODE-735.patch <br>> <br>> <br>> I replace the jar with source code, then an error will generate, when starting ODE server, I think the source code do not  match the jars which are in the war. <br>> Exception: <br>> HashMap is not an interface.(Occur in the ProcessStoreImpl.java) </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26822134 Re: Putting an ESB between ODE and the service endpoints 2009-12-16T18:24:30Z 2009-12-16T18:24:30Z Milinda Pathirage Hi Thuy, <br><br>I think you can set this property on ode-axis2.properties and it'll be use <br>when calling partner services(mean global setting). I am not sure about <br>this. Please check whether its working. <br><br>Thanks <br>Milinda <br><br><br>On Thu, Dec 17, 2009 at 2:26 AM, Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26822134&i=0" target="_top" rel="nofollow">programming@...</a>>wrote: <br><div class='shrinkable-quote'><br>> Hello, <br>> <br>> If I had an running system consisting of ODE and service endpoints, that <br>> are called by ODE. And now I want to put an ESB (for example Apache Synapse) <br>> between the ODE and the endpoints to provide loadbalancing and failover. Is <br>> there a property to define a global proxy for all outgoing calls to service <br>> endpoints or is it only possible to set the proxy in each deployment, as <br>> described here: <br>> <br>> <a href="http://ode.apache.org/user-guide.html#UserGuide-Supportedproperties" target="_top" rel="nofollow">http://ode.apache.org/user-guide.html#UserGuide-Supportedproperties</a><br>> <br>> <br>> <br>> Greetings, <br>> <br>> <br>> <br>> <br>> <br>> Thuy <br>> <br>> <br>> <br>> </div><br><br>-- <br>Milinda Pathirage <br>Senior Software Engineer & Product Manager WSO2 BPS; <a href="http://wso2.org/bps" target="_top" rel="nofollow">http://wso2.org/bps</a><br>WSO2 Inc.; <a href="http://wso2.com" target="_top" rel="nofollow">http://wso2.com</a><br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26822134&i=1" target="_top" rel="nofollow">milinda@...</a>, <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26822134&i=2" target="_top" rel="nofollow">milinda.pathirage@...</a> <br>Web: <a href="http://mpathirage.com" target="_top" rel="nofollow">http://mpathirage.com</a><br>Blog: <a href="http://blog.mpathirage.com" target="_top" rel="nofollow">http://blog.mpathirage.com</a><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26821669 [jira] Updated: (ODE-735) In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. 2009-12-16T17:29:18Z 2009-12-16T17:29:18Z JIRA jira@apache.org <br>     [ <a href="https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ] <br><br>Ma.Liang updated ODE-735: <br>------------------------- <br><br>    Fix Version/s:     (was: 1.3.4) <br>                   1.3.3 <br><div class='shrinkable-quote'><br>> In ODE version 1.3.3, replace the jar with the source code, when starting ODE server, an error will generate. java.util.HashMap is not a interface. <br>> --------------------------------------------------------------------------------------------------------------------------------------------------- <br>> <br>>                 Key: ODE-735 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-735" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-735</a><br>>             Project: ODE <br>>          Issue Type: Bug <br>>          Components: BPEL Runtime <br>>    Affects Versions: 1.3.3 <br>>         Environment: Tomcat 5.5, Apache ODE 1.3.3 <br>>            Reporter: Ma.Liang <br>>             Fix For: 1.3.3 <br>> <br>>         Attachments: ODE-735.patch <br>> <br>> <br>> I replace the jar with source code, then an error will generate, when starting ODE server, I think the source code do not  match the jars which are in the war. <br>> Exception: <br>> HashMap is not an interface.(Occur in the ProcessStoreImpl.java) </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26821630 [jira] Commented: (ODE-736) when building the project with buildr(V1.3.5), I encount an error 2009-12-16T17:25:18Z 2009-12-16T17:25:18Z JIRA jira@apache.org <br>    [ <a href="https://issues.apache.org/jira/browse/ODE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791724#action_12791724" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791724#action_12791724</a> ] <br><br>Ma.Liang commented on ODE-736: <br>------------------------------ <br><br>Greq Lucas: <br>Thank you for you attention on this problem. <br>I can not find the 1.3.x branch on <a href="http://svn.apache.org/repos/asf/ode" target="_top" rel="nofollow">http://svn.apache.org/repos/asf/ode</a>, I can get something, such as : <br><a href="http://svn.apache.org/repos/asf/ode" target="_top" rel="nofollow">http://svn.apache.org/repos/asf/ode</a><br>--branches <br>  --APACHE_ODE_1.0_INCUBATING <br>  --APACHE_ODE_1.X <br>  --bart <br>  --extvar <br>  --restful <br>  --rtver <br>--sandbox <br>--tags <br>--trunk <br><br>Would you give me a svn address about 1.3.x branch? <br><br>Thank you again! <br><div class='shrinkable-quote'><br>> when building the project with buildr(V1.3.5), I encount an error   <br>> ------------------------------------------------------------------- <br>> <br>>                 Key: ODE-736 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-736" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-736</a><br>>             Project: ODE <br>>          Issue Type: Bug <br>>          Components: Build System <br>>    Affects Versions: 1.3.3 <br>>         Environment: ruby186-27_rc2.exe  Buildr 1.3.5 <br>>            Reporter: Ma.Liang <br>>             Fix For: 1.3.3 <br>> <br>> <br>> C:\Ruby\bin\ode>buildr TEST=no ode:package <br>> (in C:/Ruby/bin/ode, development) <br>> [34mC:/Ruby/bin/ode/Buildfile:548:in `__instance_exec0': Deprecated: We changed the way package_as methods are implemen <br>> ted.  See the package method documentation for more details.[0m <br>> Buildr aborted! <br>> [31mprivate method `distro' called for project("apache-ode"):Buildr::Project[0m <br>> [31mC:/Ruby/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/application.rb:400:in `raw_load_buildfile' <br>> [0m <br>> [31mC:/Ruby/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/application.rb:218:in `load_buildfile'[0m <br>> [31mC:/Ruby/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/application.rb:213:in `load_buildfile'[0m <br>> (See full trace by running task with --trace) </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26819889 Re: org.apache.servicemix.jbi.messaging.InOnlyImpl cannot be cast to javax.jbi.messaging.InOut 2009-12-16T14:48:27Z 2009-12-16T14:48:27Z LeeCK Yes. It only happens when there's an error returned. I've opened a ticket for this issue. See <a href="https://issues.apache.org/jira/browse/ODE-740" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-740</a><br><br>Thanks! <br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color"> <div class="quote-author" style="font-weight: bold;">Rafal Rusin wrote:</div> <div class="quote-message shrinkable-quote">This happens when you use Robust In Only message exchange pattern and <br>when an error is returned for in-only request. <br>ODE assumes that when there's an error returned, jbiMex has to be in-out. <br>        } else if (jbiMex.getStatus() == ExchangeStatus.ERROR) { <br>            inOutDone((InOut) jbiMex); <br>            outFailure((InOut) jbiMex); <br>        } else if (jbiMex.getStatus() == ExchangeStatus.DONE) { <br><br>Using robust in-only IMO is not a good idea, so I suggest to modify <br>your WSDL operations to in-out or handle errors in some other way. <br>Currently ODE 1.X doesn't really support robust in-only. <br>ODE trunk has a bug <a href="https://issues.apache.org/jira/browse/ODE-464" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-464</a> , <br>which is somewhat related to this problem. <br>I think you can open ticket for it and add ODE-464 as related issue. <br><br>2009/12/15 LeeCK <leechin_kong@yahoo.com>: <br>> <br>> Hi, <br>> <br>> I am having trouble calling a webservice method that has no output. I am <br>> using Servicemix 3.3.1 with ODE 1.3.4 SNAPSHOT. Please help. Thanks. <br>> <br>> WSDL: <br>> <wsdl:types> <br>> <xs:schema attributeFormDefault="qualified" <br>> elementFormDefault="qualified" <br>> targetNamespace="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>"> <br>> <xs:element name="addstudent"> <br>> <xs:complexType> <br>> <xs:sequence> <br>> <xs:element minOccurs="0" name="studentid" <br>> nillable="true" type="xs:string"/> <br>> <xs:element minOccurs="0" name="studentname" <br>> nillable="true" type="xs:string"/> <br>> </xs:sequence> <br>> </xs:complexType> <br>> </xs:element> <br>> </xs:schema> <br>> </wsdl:types> <br>> <wsdl:message name="addstudentRequest"> <br>> <wsdl:part name="parameters" element="ns:addstudent"/> <br>> </wsdl:message> <br>> <wsdl:portType name="AddServicePortType"> <br>> <wsdl:operation name="addstudent"> <br>> <wsdl:input message="ns:addstudentRequest" <br>> wsaw:Action="urn:addstudent"/> <br>> </wsdl:operation> <br>> </wsdl:portType> <br>> <wsdl:binding name="AddServiceSoap12Binding" <br>> type="ns:AddServicePortType"> <br>> <soap12:binding transport="<a href="http://schemas.xmlsoap.org/soap/http" target="_top" rel="nofollow">http://schemas.xmlsoap.org/soap/http</a>" <br>> style="document"/> <br>> <wsdl:operation name="addstudent"> <br>> <soap12:operation soapAction="urn:addstudent" style="document"/> <br>> <wsdl:input> <br>> <soap12:body use="literal"/> <br>> </wsdl:input> <br>> </wsdl:operation> <br>> </wsdl:binding> <br>> <br>> LOG: <br>> 14:34:32,604 | ERROR | pool-flow.seda.servicemix-cxf-bc-thread-1 | <br>> CxfBcComponent | emix.common.AsyncBaseLifeCycle 537 | Error <br>> processing exchange InOnly[ <br>> id: ID:155.35.129.168-12590649523-28:0 <br>> status: Active <br>> role: provider <br>> service: {<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>}AddService <br>> endpoint: AddServiceHttpSoap12Endpoint <br>> operation: {<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>}addstudent <br>> in: <?xml version="1.0" encoding="UTF-8"?><message <br>> xmlns="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" <br>> xmlns:msgns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>" type="msgns:addstudentRequest" <br>> version="1.0"><part><addstudent xmlns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>"> <br>> <tns:studentid <br>> xmlns:tns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>">a</tns:studentid> <br>> <tns:studentname <br>> xmlns:tns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>">a</tns:studentname> <br>> </addstudent></part></message> <br>> ] <br>> javax.jbi.messaging.MessagingException: Fault not supported <br>> at <br>> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:366) <br>> at <br>> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setFault(MessageExchangeImpl.java:290) <br>> at <br>> org.apache.servicemix.cxfbc.CxfBcProvider.faultProcess(CxfBcProvider.java:277) <br>> at <br>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:261) <br>> at <br>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627) <br>> at <br>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581) <br>> at <br>> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535) <br>> at <br>> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60) <br>> at <br>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623) <br>> at <br>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172) <br>> at <br>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168) <br>> at <br>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) <br>> at <br>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) <br>> at <br>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) <br>> at java.lang.Thread.run(Thread.java:619) <br>> 14:34:32,604 | DEBUG | pool-flow.seda.servicemix-cxf-bc-thread-1 | SedaFlow <br>> | emix.jbi.nmr.flow.AbstractFlow 118 | Called Flow send <br>> 14:34:32,604 | DEBUG | pool-flow.seda.servicemix-cxf-bc-thread-2 | SedaQueue <br>> | .jbi.nmr.flow.seda.SedaQueue$1 132 | <br>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1da15c4 dequeued <br>> exchange: InOnly[ <br>> id: ID:155.35.129.168-12590649523-28:0 <br>> status: Error <br>> role: consumer <br>> service: {<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>}AddService <br>> endpoint: AddServiceHttpSoap12Endpoint <br>> operation: {<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>}addstudent <br>> in: <?xml version="1.0" encoding="UTF-8"?><message <br>> xmlns="<a href="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" target="_top" rel="nofollow">http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper</a>" <br>> xmlns:msgns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>" type="msgns:addstudentRequest" <br>> version="1.0"><part><addstudent xmlns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>"> <br>> <tns:studentid <br>> xmlns:tns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>">a</tns:studentid> <br>> <tns:studentname <br>> xmlns:tns="<a href="http://pojo.ws.jcs.test.com" target="_top" rel="nofollow">http://pojo.ws.jcs.test.com</a>">a</tns:studentname> <br>> </addstudent></part></message> <br>> error: javax.jbi.messaging.MessagingException: Fault not supported <br>> ] <br>> 14:34:32,619 | ERROR | pool-6-thread-4 | Receiver | <br>> org.apache.ode.jbi.Receiver$1 181 | Error processing JBI message. <br>> java.lang.ClassCastException: org.apache.servicemix.jbi.messaging.InOnlyImpl <br>> cannot be cast to javax.jbi.messaging.InOut <br>> at <br>> org.apache.ode.jbi.OdeConsumer.onJbiMessageExchange(OdeConsumer.java:168) <br>> at <br>> org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:44) <br>> at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179) <br>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) <br>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) <br>> at java.util.concurrent.FutureTask.run(FutureTask.java:138) <br>> at <br>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) <br>> at <br>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) <br>> at java.lang.Thread.run(Thread.java:619) <br>> <br>> -- <br>> View this message in context: <a href="http://old.nabble.com/org.apache.servicemix.jbi.messaging.InOnlyImpl-cannot-be-cast-to-javax.jbi.messaging.InOut-tp26789731p26789731.html" target="_top" rel="nofollow">http://old.nabble.com/org.apache.servicemix.jbi.messaging.InOnlyImpl-cannot-be-cast-to-javax.jbi.messaging.InOut-tp26789731p26789731.html</a><br>> Sent from the Apache Ode User mailing list archive at Nabble.com. <br>> <br>> <br><br><br><br>-- <br>Rafał Rusin <br><a href="http://rrusin.blogspot.com" target="_top" rel="nofollow">http://rrusin.blogspot.com</a><br><a href="http://www.touk.pl" target="_top" rel="nofollow">http://www.touk.pl</a><br><a href="http://top.touk.pl" target="_top" rel="nofollow">http://top.touk.pl</a></div> </div></blockquote> <p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26819834 [jira] Created: (ODE-740) ClassCastException when an error is returned for in-only request 2009-12-16T14:44:18Z 2009-12-16T14:44:18Z JIRA jira@apache.org ClassCastException when an error is returned for in-only request <br>---------------------------------------------------------------- <br><br>                 Key: ODE-740 <br>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-740" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-740</a><br>             Project: ODE <br>          Issue Type: Bug <br>          Components: Axis2 Integration <br>    Affects Versions: 1.3.4 <br>            Reporter: Lee C K <br><br><br>ClassCastException is thrown when Robust In Only message exchange pattern is used and <br>when an error is returned for the in-only request. <br><br>For more details, see <a href="http://old.nabble.com/org.apache.servicemix.jbi.messaging.InOnlyImpl-cannot-be-cast-to-javax.jbi.messaging.InOut-ts26789731.html" target="_top" rel="nofollow">http://old.nabble.com/org.apache.servicemix.jbi.messaging.InOnlyImpl-cannot-be-cast-to-javax.jbi.messaging.InOut-ts26789731.html</a><br><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26819608 Re: Generating Maven artifacts for ODE 2.0 beta2 2009-12-16T14:27:19Z 2009-12-16T14:27:19Z Daniel Dominguez Hi Dan, <br><br>I don't know how to solve your buildr issue (or if it's even solvable), <br>but you might be interested in <br><a href="http://issues.apache.org/jira/browse/ODE-729" target="_top" rel="nofollow">http://issues.apache.org/jira/browse/ODE-729</a> .  A small group of us have <br>started preliminary work on "mavenizing" ODE.  This should definitely <br>solve your problem, but the work has just begun. <br><br>-- <br>Daniel <br><br>Douglas, Dan wrote: <div class='shrinkable-quote'><br>> Ok, so I discovered "buildr install..."   <br>> <br>> My first brush created the artifacts and put them a local repository.  It generated POM files, but there was no dependency info in the files.  Buildr knows about the dependencies, is there a way to install the artifacts and generate the pom files with the dependency sections? <br>> <br>> <br>> <br>> On Dec 16, 2009, at 10:14 AM, Douglas, Dan wrote: <br>> <br>> So, I'm working on a project and we're building an integration layer implementation to front ODE with our own service pipeline.  I want to use 2.0 because we plan to use some extensions.  Our builds are Maven-based and I'd really like to pull in ODE via dependencies in our POM files, but it looks like the 2.0 libraries haven't been published to a repo anywhere (at least that I can find... I found the 1.3.3 ones). <br>> <br>> I've downloaded the 2.0-beta2 source and I've been able to build it with buildr.  I've also generated the eclipse project files.  That got me to thinking, is there some undocumented buildr incantation that generates the appropriate pom.xml files?  Is 2.0-beta2 published somewhere in a Maven repo? <br>> <br>> I'd like to get our local repo setup and was hoping to avoid having to do the tooling or conversion by hand. <br>> <br>> Dan <br>> <br>> <br>>   <br></div><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26819390 Re: Generating Maven artifacts for ODE 2.0 beta2 2009-12-16T14:11:42Z 2009-12-16T14:11:42Z Douglas, Dan Ok, so I discovered "buildr install..."   <br><br>My first brush created the artifacts and put them a local repository.  It generated POM files, but there was no dependency info in the files.  Buildr knows about the dependencies, is there a way to install the artifacts and generate the pom files with the dependency sections? <br><br><br><br>On Dec 16, 2009, at 10:14 AM, Douglas, Dan wrote: <br><br>So, I'm working on a project and we're building an integration layer implementation to front ODE with our own service pipeline.  I want to use 2.0 because we plan to use some extensions.  Our builds are Maven-based and I'd really like to pull in ODE via dependencies in our POM files, but it looks like the 2.0 libraries haven't been published to a repo anywhere (at least that I can find... I found the 1.3.3 ones). <br><br>I've downloaded the 2.0-beta2 source and I've been able to build it with buildr.  I've also generated the eclipse project files.  That got me to thinking, is there some undocumented buildr incantation that generates the appropriate pom.xml files?  Is 2.0-beta2 published somewhere in a Maven repo? <br><br>I'd like to get our local repo setup and was hoping to avoid having to do the tooling or conversion by hand. <br><br>Dan <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26819119 [jira] Commented: (ODE-739) Add recoverActivity command 2009-12-16T13:52:18Z 2009-12-16T13:52:18Z JIRA jira@apache.org <br>    [ <a href="https://issues.apache.org/jira/browse/ODE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791603#action_12791603" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791603#action_12791603</a> ] <br><br>Daniel Dominguez commented on ODE-739: <br>-------------------------------------- <br><br>Installation in ServiceMix is identical to ODE-706. <br><br>From the karaf shell you can do: <br><br>karaf@root> ode:recoverActivity --help <br>DESCRIPTION <br>        ode:recoverActivity <br><br>        Recover an ode activity <br><br>SYNTAX <br>        ode:recoverActivity [options] iid aid <br><br>ARGUMENTS <br>        iid            Instance ID <br>        aid            Activity IDs to attempt recovery <br><br>OPTIONS <br>        -f, --fault <br>                       Fault the activity (default=retry) <br>        -r, --retry <br>                       Retry the activity (default=retry) <br>        -c, --cancel <br>                       Cancel the activity (default=retry) <br>        --help <br>                       Display this help message <br><br><div class='shrinkable-quote'><br>> Add recoverActivity command <br>> --------------------------- <br>> <br>>                 Key: ODE-739 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-739" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-739</a><br>>             Project: ODE <br>>          Issue Type: Sub-task <br>>    Affects Versions: 1.3.4 <br>>            Reporter: Daniel Dominguez <br>>         Attachments: ODE-739.patch <br>> <br>> <br>> Tammo van Lessen suggested adding support for recoverActivity </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26819059 [jira] Updated: (ODE-739) Add recoverActivity command 2009-12-16T13:48:18Z 2009-12-16T13:48:18Z JIRA jira@apache.org <br>     [ <a href="https://issues.apache.org/jira/browse/ODE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ] <br><br>Daniel Dominguez updated ODE-739: <br>--------------------------------- <br><br>    Attachment: ODE-739.patch <br><br>Initial contribution for ODE-739 <br><div class='shrinkable-quote'><br>> Add recoverActivity command <br>> --------------------------- <br>> <br>>                 Key: ODE-739 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-739" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-739</a><br>>             Project: ODE <br>>          Issue Type: Sub-task <br>>    Affects Versions: 1.3.4 <br>>            Reporter: Daniel Dominguez <br>>         Attachments: ODE-739.patch <br>> <br>> <br>> Tammo van Lessen suggested adding support for recoverActivity </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26818373 [jira] Created: (ODE-739) Add recoverActivity command 2009-12-16T13:00:18Z 2009-12-16T13:00:18Z JIRA jira@apache.org Add recoverActivity command <br>--------------------------- <br><br>                 Key: ODE-739 <br>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-739" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-739</a><br>             Project: ODE <br>          Issue Type: Sub-task <br>    Affects Versions: 1.3.4 <br>            Reporter: Daniel Dominguez <br><br><br>Tammo van Lessen suggested adding support for recoverActivity <br><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26818315 Putting an ESB between ODE and the service endpoints 2009-12-16T12:56:41Z 2009-12-16T12:56:41Z BA Hello, <br><br>If I had an running system consisting of ODE and service endpoints, that are called by ODE. And now I want to put an ESB (for example Apache Synapse) between the ODE and the endpoints to provide loadbalancing and failover. Is there a property to define a global proxy for all outgoing calls to service endpoints or is it only possible to set the proxy in each deployment, as described here: <br><br><a href="http://ode.apache.org/user-guide.html#UserGuide-Supportedproperties" target="_top" rel="nofollow">http://ode.apache.org/user-guide.html#UserGuide-Supportedproperties</a><br><br>  <br><br>Greetings, <br><br>  <br><br>  <br><br>Thuy <br><br>  <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26817190 Re: ODE & Tomcat & Mysql Error 2009-12-16T11:38:55Z 2009-12-16T11:38:55Z Andreas Fritzler Ok Problem solved: <br><br>ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ODEDB <br><br>instead of <br><br>ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode <br><br>in the axis2.properties. <br><br><br><br>On Wed, Dec 16, 2009 at 14:17, Andreas Fritzler <br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26817190&i=0" target="_top" rel="nofollow">andreas.fritzler@...</a>> wrote: <div class='shrinkable-quote'><br>> Hi, <br>> <br>> I'm trying to get ODE running with mysql and I'm getting the following <br>> Error when I start tomcat. <br>> <br>> ERROR [Database] Failed to resolved external DataSource at <br>> "java:comp/env/jdbc/ode". <br>> <br>> Tomcat server.xml: <br>> <br>> <Context path="/ode" docBase="ode" debug="5" reloadable="true" <br>> crossContext="true"> <br>> <Resource name="jdbc/ODEDB" auth="Container" type="javax.sql.DataSource" <br>> maxActive="100" maxIdle="30" maxWait="10000" <br>> username="root" password="admin" driverClassName="com.mysql.jdbc.Driver" <br>> url="jdbc:mysql://localhost:3306/ode?autoReconnect=true"/> <br>> </Context> <br>> <br>> In the axis2.properties: <br>> <br>> ode-axis2.db.mode=EXTERNAL <br>> ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode <br>> <br>> Anybody an idea what the problem here is? <br>> <br>> Cheers, <br>> Andreas <br>> <br></div><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26816816 ODE & Tomcat & Mysql Error 2009-12-16T11:17:06Z 2009-12-16T11:17:06Z Andreas Fritzler Hi, <br><br>I'm trying to get ODE running with mysql and I'm getting the following <br>Error when I start tomcat. <br><br>ERROR [Database] Failed to resolved external DataSource at <br>"java:comp/env/jdbc/ode". <br><br>Tomcat server.xml: <br><br><Context path="/ode" docBase="ode" debug="5" reloadable="true" <br>crossContext="true"> <br><Resource name="jdbc/ODEDB" auth="Container" type="javax.sql.DataSource" <br>        maxActive="100" maxIdle="30" maxWait="10000" <br>        username="root" password="admin" driverClassName="com.mysql.jdbc.Driver" <br>        url="jdbc:mysql://localhost:3306/ode?autoReconnect=true"/> <br></Context> <br><br>In the axis2.properties: <br><br>ode-axis2.db.mode=EXTERNAL <br>ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode <br><br>Anybody an idea what the problem here is? <br><br>Cheers, <br>Andreas <br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26815825 Generating Maven artifacts for ODE 2.0 beta2 2009-12-16T10:14:30Z 2009-12-16T10:14:30Z Douglas, Dan So, I'm working on a project and we're building an integration layer implementation to front ODE with our own service pipeline.  I want to use 2.0 because we plan to use some extensions.  Our builds are Maven-based and I'd really like to pull in ODE via dependencies in our POM files, but it looks like the 2.0 libraries haven't been published to a repo anywhere (at least that I can find... I found the 1.3.3 ones). <br><br>I've downloaded the 2.0-beta2 source and I've been able to build it with buildr.  I've also generated the eclipse project files.  That got me to thinking, is there some undocumented buildr incantation that generates the appropriate pom.xml files?  Is 2.0-beta2 published somewhere in a Maven repo? <br><br>I'd like to get our local repo setup and was hoping to avoid having to do the tooling or conversion by hand. <br><br>Dan<p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26812921 scheduled job after breakpoint 2009-12-16T07:28:30Z 2009-12-16T07:28:30Z Marco Indaco Hello, <br>i have, for my research project, added a patch developed by Denis for <br>debug support as web service. (Google summer of code). <br>I have made some trial adding breakpoint on instances process. That's ok. <br>But when i re-start Jboss AS i obtain a large number of errors. They <br>are messages which are blocked with breakpoint. <br><br>see below one of them extract from log... <br><br>16:19:43,204 INFO  [STDOUT] INFO - BpelServerImpl.call(517) | Received a sched <br>uled job event for inactive process {<a href="http://www.jboss.org/bpel/examples" target="_top" rel="nofollow">http://www.jboss.org/bpel/examples</a>}SimpleIn <br>voke-5; rescheduling job hqejbhcnphr4u1xh1bgkv4 <br><br>I received that error after i remove a process definitively.(But i <br>obtain similar error also when process is active!!!) <br><br>Thank in advance for any information about that. <br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26812601 Re: Changing Endpoints of a Process Instance at RUNTIME 2009-12-16T07:10:31Z 2009-12-16T07:10:31Z Marco Indaco Hello, <br>I tried the second opportunity that i have signaled to you and with <br>.endpoint file there are 30 second for refresh operation. <br>However let me know. <br><br>Best Regards <br><br>2009/12/16 Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=0" target="_top" rel="nofollow">programming@...</a>>: <div class='shrinkable-quote'><br>> Hello, <br>> Thanks for pointing out where to start looking and extending ODE. That's roughly what I'm looking for. I will let you know if I succeed. <br>> Any additional hints and ideas would still be appreciated! <br>> <br>> Best regards, <br>> <br>> <br>> Thuy <br>> <br>>> -----Original Message----- <br>>> From: Tammo van Lessen [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=1" target="_top" rel="nofollow">tvanlessen@...</a>] <br>>> Sent: Tuesday, December 15, 2009 10:40 PM <br>>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=2" target="_top" rel="nofollow">user@...</a> <br>>> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>>> <br>>> Hi, <br>>> <br>>> As an academic I'd also go with slightly extending ODE. The Instance <br>>> Management API is definitely a good starting point for that, I'd start <br>>> with adding a new method to <br>>> org.apache.ode.bpel.pmapi.InstanceManagement <br>>> and implement it in <br>>> org.apache.ode.bpel.engine.ProcessAndInstanceManagementImpl. The code <br>>> for modifying the EPR of a partner link can be derived from ASSIGN <br>>> and/or AssignHelper. <br>>> <br>>> HTH, <br>>> Tammo <br>>> <br>>> On 15.12.2009 21:46, Song Thuy Nguyen wrote: <br>>> > Setting up a proxy is seen as one of the less desireable solution, <br>>> because it would create a single point of failure. Incase the proxy <br>>> component fails, the whole BPEL engine will stop working. Our system <br>>> (as it is designed) as mentioned uses normal BPEL files without any <br>>> dynamic binding capability, so it would also work if the proces <br>>> instance rebinding component (which I'm trying to implement) fails. The <br>>> system then would run like a normal BPEL engine without fault <br>>> compensation ability. <br>>> > I will look into the WS-Policy, maybe this will work for me, thank <br>>> you! <br>>> > <br>>> > If anyone has another idea, especially how to extend ODE itself like <br>>> in my first post, please let me know. <br>>> > <br>>> > Best regards, <br>>> > <br>>> > Thuy <br>>> > <br>>> > <br>>> >> -----Original Message----- <br>>> >> From: Ford, Mark - 0661 - MITLL [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=3" target="_top" rel="nofollow">mark.ford@...</a>] <br>>> >> Sent: Tuesday, December 15, 2009 8:18 PM <br>>> >> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=4" target="_top" rel="nofollow">user@...</a> <br>>> >> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>>> >> <br>>> >> Have you considered setting up a proxy service that would handle <br>>> >> retries or address rewriting? This would keep your BPEL simple since <br>>> >> all of the changes are external to the BPEL and in fact external to <br>>> >> ODE. Another option would be to modify the invoke layer for ODE to <br>>> >> provide this behavior keyed off of WS-Policy. For a sample <br>>> >> implementation of this policy, check out the docs here: <br>>> >> <a href="http://tinyurl.com/ya4tmsk" target="_top" rel="nofollow">http://tinyurl.com/ya4tmsk</a><br>>> >> <br>>> >> <br>>> >> <br>>> >> On Dec 15, 2009, at 10:51 AM, Song Thuy Nguyen wrote: <br>>> >> <br>>> >>> Hi Marco, <br>>> >>> Thanks for the fast answer and your suggestion, but the 2 links you <br>>> >>> gave me <br>>> >>> are not suitable for this problem. I read all the user manual of <br>>> >>> apache ode <br>>> >>> on the website before but didn't find any solution. The first link <br>>> >>> describes <br>>> >>> HOW endpoints can be represented, and the second one, as far as I <br>>> >>> understand <br>>> >>> describe is a way to manipulate endpoints on a process-wide level, <br>>> >>> and there <br>>> >>> is also a second problem with this solution (copied from <br>>> >>> <a href="http://ode.apache.org/endpoint-configuration.html):" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html):</a><br>>> >>> <br>>> >>> " Dynamic refresh <br>>> >>> <br>>> >>> Properties are dynamically loaded and refreshed at run time. <br>>> >>> The timing is the following: <br>>> >>> On every request, if the file has not been polled during the last <br>>> 30 <br>>> >>> seconds <br>>> >>> then check the file for updates. If any, reload it. <br>>> >>> <br>>> >>> Consequently, if you have updated properties, you have to wait ~30 <br>>> >>> seconds <br>>> >>> and then trigger a request." <br>>> >>> <br>>> >>> so you have to wait up to 30s to see the changes taking effect. <br>>> >> That's <br>>> >>> "ages" considering you are stopping a running instance to replace <br>>> an <br>>> >>> endpoint and continue. <br>>> >>> <br>>> >>> Looks like the 3rd suggestion is the only way to go. I'll let you <br>>> >>> know if I <br>>> >>> find an applicable concrete solution. <br>>> >>> <br>>> >>> Is there someone else with another solution for me? :) <br>>> >>> <br>>> >>> Regards, <br>>> >>> <br>>> >>> Thuy <br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> -----Ursprüngliche Nachricht----- <br>>> >>> Von: Marco Indaco [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=5" target="_top" rel="nofollow">marco.indaco@...</a>] <br>>> >>> Gesendet: Dienstag, 15. Dezember 2009 14:52 <br>>> >>> An: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=6" target="_top" rel="nofollow">user@...</a> <br>>> >>> Betreff: Re: Changing Endpoints of a Process Instance at RUNTIME <br>>> >>> <br>>> >>> Hi song, <br>>> >>> i'am working on your own objective, in my research project. <br>>> >>> There are many solution that you can investigate. <br>>> >>> <br>>> >>> 1) <a href="http://ode.apache.org/endpoint-references.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-references.html</a>  see that link <br>>> >>> <br>>> >>> 2)Create, if monitor observes, for example, that a service is down, <br>>> a <br>>> >>> file .endpoint located in conf directory in Apache Ode. see that <br>>> link <br>>> >>> <a href="http://ode.apache.org/endpoint-configuration.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html</a><br>>> >>> <br>>> >>> 3) A more intrusive operation for modify source code to added these <br>>> >>> functionalites <br>>> >>> <br>>> >>> If you are any idea please contact me...working together is <br>>> powerful. <br>>> >>> <br>>> >>> Hi, for any question ask me!!! <br>>> >>> <br>>> >>> 2009/12/15 Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812601&i=7" target="_top" rel="nofollow">programming@...</a>>: <br>>> >>>> Hi everyone, <br>>> >>>> <br>>> >>>> <br>>> >>>> <br>>> >>>> I'm quite new to Apache ODE and mailing lists, hoping for your <br>>> help. <br>>> >>>> <br>>> >>>> As the title says I'm looking for a way to change service <br>>> endpoints <br>>> >>>> for <br>>> >>> BPEL <br>>> >>>> process instances at runtime. That means that only one instance <br>>> >>>> should be <br>>> >>>> affected by these changes, not the entire process and the <br>>> deployment <br>>> >>>> descriptor. By convention of the project I'm working on, it is not <br>>> >>>> allowed <br>>> >>>> to write a BPEL-process that looks up service endpoints at a <br>>> >> registry <br>>> >>>> service, put it in an variable and use it as the dynamic <br>>> endpoint. <br>>> >>>> The <br>>> >>>> reason is we want to provide a fault resistant BPEL process <br>>> >>>> execution by <br>>> >>>> replacing failing or unavailabe service endpoints by working ones <br>>> >>>> with <br>>> >>>> transparency to the process. So there should be no sign of the <br>>> >> "fault <br>>> >>>> handling" in the BPEL file. Failing services will be detected by a <br>>> >>>> monitor <br>>> >>>> component, but this is not my part. <br>>> >>>> <br>>> >>>> I have tried to look into the Management API for processes and <br>>> >>>> instances <br>>> >>> to <br>>> >>>> find a method that can provide a solution, but I had no luck. <br>>> There <br>>> >>>> are <br>>> >>> only <br>>> >>>> methods to get and set endpoints on a process-wide level, on a <br>>> >>>> instance <br>>> >>>> level however, those methods are not available. <br>>> >>>> <br>>> >>>> It seems to me that the only way to get such a functionality is to <br>>> >>>> extend <br>>> >>>> the Instance Management API and write those methods myself, If <br>>> this <br>>> >>>> is <br>>> >>>> right, can someone please tell me where to start? Any help would <br>>> be <br>>> >>>> appreciated. <br>>> >>>> <br>>> >>>> <br>>> >>>> <br>>> >>>> Thank you in advance <br>>> >>>> <br>>> >>>> <br>>> >>>> <br>>> >>>> Thuy <br>>> >>>> <br>>> >>>> <br>>> >>> <br>>> >>> __________ Information from ESET NOD32 Antivirus, version of virus <br>>> >>> signature <br>>> >>> database 4689 (20091215) __________ <br>>> >>> <br>>> >>> The message was checked by ESET NOD32 Antivirus. <br>>> >>> <br>>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>> >>> Version 4634 <br>>> >>> (20091124) __________ <br>>> >>> <br>>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>> >>> <br>>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>> >>> Version 4634 <br>>> >>> (20091124) __________ <br>>> >>> <br>>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>> >>> <br>>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>> >>> <br>>> >>> <br>>> >>> <br>>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>> >>> Version 4634 <br>>> >>> (20091124) __________ <br>>> >>> <br>>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>> >>> <br>>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>> >>> <br>>> >>> <br>>> >> <br>>> >> <br>>> >> <br>>> >> <br>>> >> -- <br>>> >> Mark Ford <br>>> >> MIT Lincoln Laboratory <br>>> >> 244 Wood Street <br>>> >> Lexington MA 02420 <br>>> >> (781) 981-1843 <br>>> > <br>>> > <br>>> <br>>> <br>>> -- <br>>> Tammo van Lessen - <a href="http://www.taval.de" target="_top" rel="nofollow">http://www.taval.de</a><br>> <br>> <br></div><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26812071 Re: Maven Build system design (was Re: build failed in trunk - I wish we had maven) 2009-12-16T06:37:25Z 2009-12-16T06:37:25Z Kurt T Stam-4 Thanks Jeff, <br><br>Let's make sure we keep the wiki page update so that we  document what <br>build functionality each module has. This should make it easier to keep <br>the two build systems in sync. <br><br>Also let's try to get our feature wishes in, so we can agree on the <br>needs we are trying to solve for. <br><br>--Kurt <br><br>Jeff Yu wrote: <div class='shrinkable-quote'><br>> FYI, I've already started working on this task. <br>> <br>> Currently finished the parent (project pom), utils, jacob-ap, jacob. and <br>> working on the bpel-schema at the moment. <br>> If you started working on a module, it is better that you update the wiki, <br>> or follow up this thread to say which module you are working on, so that you <br>> won't double our efforts. ;-) <br>> <br>> Regards <br>> Jeff <br>> <br>> On Tue, Dec 15, 2009 at 1:46 AM, Kurt T Stam <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812071&i=0" target="_top" rel="nofollow">kurt.stam@...</a>> wrote: <br>>   <br>>> I created a new page: <a href="http://wiki.apache.org/ode/MavenBuildDesignApacheODE" target="_top" rel="nofollow">http://wiki.apache.org/ode/MavenBuildDesignApacheODE</a><br>>> . <br>>> <br>>> Cheers, <br>>> <br>>> --Kurt <br>>> <br>>> <br>>>     <br>> <br>>   </div><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26811911 Re: Callback to a process 2009-12-16T06:28:57Z 2009-12-16T06:28:57Z dawg Thanks Greg, it helps in understanding, the problem is that it is a bit intrusive on the invoked web services. Is there a way to do it without forcing the partner links having to receive the process id as parameter? <br><br>With regards to ODE specific extensions, is there anything that could be useful for what I want to do? (I don't mind portability much, it's a research project rather than a product) <br><br>Thanks, <br>Dawg <br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color"> <div class="quote-author" style="font-weight: bold;">Greg Lucas-3 wrote:</div> <div class="quote-message shrinkable-quote">Hi Dawg, <br><br>Ignoring engine-specific extensions, a BPEL correlation set is initialized   <br>as part of a messaging activity (receive/invoke/reply/onMessage/onEvent)   <br>based on properties of the incoming or outgoing message. On a messaging   <br>activity you can identify the correlation set(s) for that message and   <br>whether each correlation set should be initiated. (There's also a third   <br>option called join, which means initialize the correlation set if it   <br>hasn't yet been initialized - take a look at BPEL spec for details.) <br><br>So correlation sets are not like variables that you assign directly, but   <br>are initialized based on content of a message being sent or received. ODE   <br>provides an extension to get the process id (ode:pid). The typical way to   <br>do what you describe would be to invoke some partner link and include the   <br>pid in the outgoing message, initiating the correlation set from the   <br>message as part of the invoke. You can then use that correlation set to   <br>correlate a receive for the same or another partner link. <br><br>Does that help? <br><br>On Wed, 16 Dec 2009 06:35:54 -0500, dawg <zohar.etzioni@gmail.com> wrote: <br><br>> <br>> I'm sure I need an extra partner link, and so I did add another port   <br>> type to <br>> the process wsdl which should be mapped to the receive activity. As for   <br>> the <br>> rest, I'm not sure I understand how that works. What does "initiate <br>> correlation set" mean? If I'm basing my correlation to the process   <br>> instance <br>> by instance id which is a part of the callback message, it means that all <br>> other activities have nothing really to bind to the correlation set, so   <br>> I'm <br>> not sure what would attaching correlation set to this activities do. <br>> Another question is how would I "initialise" the correlation set with the <br>> process id so that when it has to be matched later with the callback   <br>> part, <br>> it would be able to. <br>> <br>> Given the following example simple workflow attached with a receive1   <br>> which <br>> activates the workflow, invoking some activity on a web service and <br>> returning the result, with parallel receive for receiving the callback,   <br>> how <br>> can I configure the correlation such that messages having the part   <br>> process <br>> id equals the process instance id will join the running instance rather   <br>> than <br>> create a new one? <br>> <br>> <a href="http://old.nabble.com/file/p26809806/Picture%2B2.png" target="_top" rel="nofollow">http://old.nabble.com/file/p26809806/Picture%2B2.png</a> Picture+2.png <br>> <br>> I created a property called process id: <br>> <br>> <vprop:property name="processId" type="xsd:string"/> <br>> <br>> and added a alias for the callback message part: <br>> <br>> <vprop:propertyAlias <br>> messageType="tns:MediaCompositeFaultCallbackOperationRequest" part="pid" <br>> propertyName="tns:processId"/> <br>> <br>> But that surely is not enough. For one thing there needs to be a way to   <br>> say <br>> that I want to match the incoming message part process id with a variable <br>> from the process. Another thing is what must be done with regards to <br>> correlation for the rest of the invoke/receive activities. <br>> <br>> Thanks, <br>> Dawg <br>> <br>> <br>> Greg Lucas-3 wrote: <br>>> <br>>> Sorry, hit send by mistake. <br>>> <br>>> You will need a partner link for the receive, but it does not have to   <br>>> be a <br>>> partner link used elsewhere in the process. You will also need to   <br>>> initiate <br>>> the correlation set prior to the async receive; but you can do that on a <br>>> message activity associated with a different partner link. For example, <br>>> you might initiate the correlation set on the receive activity that <br>>> instantiates the process instance, or on some invocation of another <br>>> partner link that happens before entering the scope with your async <br>>> receive. <br>>> <br>>> <br>>> ~Greg <br>>> <br>>> On Tue, 15 Dec 2009 16:00:03 -0500, Greg Lucas <greg.lucas@gmail.com> <br>>> wrote: <br>>> <br>>>> For this to work you'll need: <br>>>>   - a partner link for the receive activbity <br>>>> <br>>>> <br>>>> <br>>>> On Tue, 15 Dec 2009 15:07:05 -0500, dawg <zohar.etzioni@gmail.com>   <br>>>> wrote: <br>>>> <br>>>>> <br>>>>> Hi, <br>>>>> <br>>>>> Here's what I'm trying to do: <br>>>>> In parallel to the whole execution flow of the process, I want to have <br>>>>> another receive activity that would be able to receive a message. Now <br>>>>> the <br>>>>> match between the process to select and the message sent can be based <br>>>>> on the <br>>>>> process id, so it is reasonable to assume that the sender has it. This <br>>>>> is <br>>>>> the use case (or its vague version). <br>>>>> <br>>>>> I thought I'd be able to implement that with correlation sets, but I'm <br>>>>> not <br>>>>> sure that's correct. The problem is that this callback message is not <br>>>>> sent <br>>>>> from any of the partner links, and has no direct relation to any   <br>>>>> invoke <br>>>>> activity. So what I really want is that every other message that is <br>>>>> directed <br>>>>> to this process will create a new instance, while this message will be <br>>>>> directed to the process which has this process id. <br>>>>> <br>>>>> Assuming I created a property process Id, and created an alias to it <br>>>>> from <br>>>>> the message part that matches the callback message, and defined and <br>>>>> attached <br>>>>> the correlation set to this callback receive activity. How do I <br>>>>> initialise <br>>>>> the process id to match with? why do I have to attach the correlation <br>>>>> set <br>>>>> (if I do) to all invoke/receive activities? <br>>>>> <br>>>>> Perhaps correlation sets are not the right solution to my problem. In <br>>>>> that <br>>>>> case, any other ideas? <br><br>-- <br>Greg Lucas </div> </div></blockquote> <p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26811903 Re: Maven Build system design (was Re: build failed in trunk - I wish we had maven) 2009-12-16T06:27:39Z 2009-12-16T06:27:39Z Jeff Yu FYI, I've already started working on this task. <br><br>Currently finished the parent (project pom), utils, jacob-ap, jacob. and <br>working on the bpel-schema at the moment. <br>If you started working on a module, it is better that you update the wiki, <br>or follow up this thread to say which module you are working on, so that you <br>won't double our efforts. ;-) <br><br>Regards <br>Jeff <br><br>On Tue, Dec 15, 2009 at 1:46 AM, Kurt T Stam <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26811903&i=0" target="_top" rel="nofollow">kurt.stam@...</a>> wrote: <div class='shrinkable-quote'><br>> <br>> <br>> I created a new page: <a href="http://wiki.apache.org/ode/MavenBuildDesignApacheODE" target="_top" rel="nofollow">http://wiki.apache.org/ode/MavenBuildDesignApacheODE</a><br>> . <br>> <br>> Cheers, <br>> <br>> --Kurt <br>> <br>> </div><br>-- <br>Cheers, <br>Jeff Yu <br><br>---------------- <br>blog: <a href="http://jeff.familyyu.net" target="_top" rel="nofollow">http://jeff.familyyu.net</a><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26811833 [jira] Commented: (ODE-729) Consider moving to maven 2009-12-16T06:23:18Z 2009-12-16T06:23:18Z JIRA jira@apache.org <br>    [ <a href="https://issues.apache.org/jira/browse/ODE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791379#action_12791379" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791379#action_12791379</a> ] <br><br>Jeff Yu commented on ODE-729: <br>----------------------------- <br><br>Kurt has created a wiki at: <a href="http://wiki.apache.org/ode/MavenBuildDesignApacheODE" target="_top" rel="nofollow">http://wiki.apache.org/ode/MavenBuildDesignApacheODE</a><br><div class='shrinkable-quote'><br>> Consider moving to maven <br>> ------------------------ <br>> <br>>                 Key: ODE-729 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-729" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-729</a><br>>             Project: ODE <br>>          Issue Type: New Feature <br>>          Components: Build System <br>>    Affects Versions: Wishlist <br>>            Reporter: Greg Lucas <br>> <br>> This was recently discussed on IRC so I'm raising a JIRA to track further comments and gauge interest: Should ODE consider adopting a Maven 2 (or maven 3) build? <br>> Maven has become widely adopted for open source and is used for many popular Apache projects. Developers coming to ODE are likely to be familiar with maven and already be using tools (such as IDEs, continuous integration servers, etc) that have built-in support for maven poms. In some scenarios the more complex maven dependency mechanisms for transitive and scoped dependencies would be useful for ODE developers and users. <br>> Is the ODE community interested in a maven-based build? Can maven handle the complexities of ODE's packaging? </div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26810936 Re: Callback to a process 2009-12-16T05:21:40Z 2009-12-16T05:21:40Z Greg Lucas-3 Hi Dawg, <br><br>Ignoring engine-specific extensions, a BPEL correlation set is initialized   <br>as part of a messaging activity (receive/invoke/reply/onMessage/onEvent)   <br>based on properties of the incoming or outgoing message. On a messaging   <br>activity you can identify the correlation set(s) for that message and   <br>whether each correlation set should be initiated. (There's also a third   <br>option called join, which means initialize the correlation set if it   <br>hasn't yet been initialized - take a look at BPEL spec for details.) <br><br>So correlation sets are not like variables that you assign directly, but   <br>are initialized based on content of a message being sent or received. ODE   <br>provides an extension to get the process id (ode:pid). The typical way to   <br>do what you describe would be to invoke some partner link and include the   <br>pid in the outgoing message, initiating the correlation set from the   <br>message as part of the invoke. You can then use that correlation set to   <br>correlate a receive for the same or another partner link. <br><br>Does that help? <br><br>On Wed, 16 Dec 2009 06:35:54 -0500, dawg <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810936&i=0" target="_top" rel="nofollow">zohar.etzioni@...</a>> wrote: <br><div class='shrinkable-quote'><br>> <br>> I'm sure I need an extra partner link, and so I did add another port   <br>> type to <br>> the process wsdl which should be mapped to the receive activity. As for   <br>> the <br>> rest, I'm not sure I understand how that works. What does "initiate <br>> correlation set" mean? If I'm basing my correlation to the process   <br>> instance <br>> by instance id which is a part of the callback message, it means that all <br>> other activities have nothing really to bind to the correlation set, so   <br>> I'm <br>> not sure what would attaching correlation set to this activities do. <br>> Another question is how would I "initialise" the correlation set with the <br>> process id so that when it has to be matched later with the callback   <br>> part, <br>> it would be able to. <br>> <br>> Given the following example simple workflow attached with a receive1   <br>> which <br>> activates the workflow, invoking some activity on a web service and <br>> returning the result, with parallel receive for receiving the callback,   <br>> how <br>> can I configure the correlation such that messages having the part   <br>> process <br>> id equals the process instance id will join the running instance rather   <br>> than <br>> create a new one? <br>> <br>> <a href="http://old.nabble.com/file/p26809806/Picture%2B2.png" target="_top" rel="nofollow">http://old.nabble.com/file/p26809806/Picture%2B2.png</a> Picture+2.png <br>> <br>> I created a property called process id: <br>> <br>> <vprop:property name="processId" type="xsd:string"/> <br>> <br>> and added a alias for the callback message part: <br>> <br>> <vprop:propertyAlias <br>> messageType="tns:MediaCompositeFaultCallbackOperationRequest" part="pid" <br>> propertyName="tns:processId"/> <br>> <br>> But that surely is not enough. For one thing there needs to be a way to   <br>> say <br>> that I want to match the incoming message part process id with a variable <br>> from the process. Another thing is what must be done with regards to <br>> correlation for the rest of the invoke/receive activities. <br>> <br>> Thanks, <br>> Dawg <br>> <br>> <br>> Greg Lucas-3 wrote: <br>>> <br>>> Sorry, hit send by mistake. <br>>> <br>>> You will need a partner link for the receive, but it does not have to   <br>>> be a <br>>> partner link used elsewhere in the process. You will also need to   <br>>> initiate <br>>> the correlation set prior to the async receive; but you can do that on a <br>>> message activity associated with a different partner link. For example, <br>>> you might initiate the correlation set on the receive activity that <br>>> instantiates the process instance, or on some invocation of another <br>>> partner link that happens before entering the scope with your async <br>>> receive. <br>>> <br>>> <br>>> ~Greg <br>>> <br>>> On Tue, 15 Dec 2009 16:00:03 -0500, Greg Lucas <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810936&i=1" target="_top" rel="nofollow">greg.lucas@...</a>> <br>>> wrote: <br>>> <br>>>> For this to work you'll need: <br>>>>   - a partner link for the receive activbity <br>>>> <br>>>> <br>>>> <br>>>> On Tue, 15 Dec 2009 15:07:05 -0500, dawg <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810936&i=2" target="_top" rel="nofollow">zohar.etzioni@...</a>>   <br>>>> wrote: <br>>>> <br>>>>> <br>>>>> Hi, <br>>>>> <br>>>>> Here's what I'm trying to do: <br>>>>> In parallel to the whole execution flow of the process, I want to have <br>>>>> another receive activity that would be able to receive a message. Now <br>>>>> the <br>>>>> match between the process to select and the message sent can be based <br>>>>> on the <br>>>>> process id, so it is reasonable to assume that the sender has it. This <br>>>>> is <br>>>>> the use case (or its vague version). <br>>>>> <br>>>>> I thought I'd be able to implement that with correlation sets, but I'm <br>>>>> not <br>>>>> sure that's correct. The problem is that this callback message is not <br>>>>> sent <br>>>>> from any of the partner links, and has no direct relation to any   <br>>>>> invoke <br>>>>> activity. So what I really want is that every other message that is <br>>>>> directed <br>>>>> to this process will create a new instance, while this message will be <br>>>>> directed to the process which has this process id. <br>>>>> <br>>>>> Assuming I created a property process Id, and created an alias to it <br>>>>> from <br>>>>> the message part that matches the callback message, and defined and <br>>>>> attached <br>>>>> the correlation set to this callback receive activity. How do I <br>>>>> initialise <br>>>>> the process id to match with? why do I have to attach the correlation <br>>>>> set <br>>>>> (if I do) to all invoke/receive activities? <br>>>>> <br>>>>> Perhaps correlation sets are not the right solution to my problem. In <br>>>>> that <br>>>>> case, any other ideas? </div><br>-- <br>Greg Lucas <br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26810130 RE: Extend InstanceManagement API to provide endpoint manipulation 2009-12-16T04:06:48Z 2009-12-16T04:06:48Z BA Thank you for this suggestion. It seems to be a every efficient and practical sollution. Now I have to check back with the others in my project and see how much work it would create to integrate an ESB in our system. For now ODE communicates directly with service endpoints, there is no ESB or MoM in between. I wonder why my people did not design the system with an ESB in the first place... academics! :D <br><br>Greetings, <br><br>Thuy <br><div class='shrinkable-quote'><br>> -----Original Message----- <br>> From: Milinda Pathirage [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=0" target="_top" rel="nofollow">milinda.pathirage@...</a>] <br>> Sent: Wednesday, December 16, 2009 4:52 AM <br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=1" target="_top" rel="nofollow">dev@...</a> <br>> Subject: Re: Extend InstanceManagement API to provide endpoint <br>> manipulation <br>> <br>> I also think that calling the service through a ESB will be a better <br>> alternative your approach. In this way you can use ESB to handle fail- <br>> over <br>> and failure handling is transparent to your BPEL. I think changing <br>> instance <br>> at runtime is not a good solution for this scenario. You can use Apache <br>> Synapse to handle fail-over. Please look endpoint section of article <br>> at[1]. <br>> <br>> Thanks <br>> Milinda <br>> <br>> [1] <a href="http://wso2.org/library/2559" target="_top" rel="nofollow">http://wso2.org/library/2559</a><br>> <br>> On Wed, Dec 16, 2009 at 2:01 AM, Song Thuy Nguyen <br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=2" target="_top" rel="nofollow">programming@...</a>>wrote: <br>> <br>> > Hello Greg, <br>> > <br>> > > Wouldn't you also need to detect the <br>> > > failure and retry the failed activity? Would you also want all <br>> subsequent <br>> > > process instances to use the new endpoint, or would you expect each <br>> new <br>> > > instance to try the original ep and fail over as well? <br>> > <br>> > Once there is a failure calling a service endpoint, the process <br>> instance <br>> > execution will be paused, the new endpoint will be written over the <br>> old ones <br>> > and the processinstance will then be continued trying to call the <br>> last <br>> > action (new calling for the new endpoint). This solution is a kind of <br>> > "optimistic aproach" where service unavailability is mostly temporaly <br>> and <br>> > the next call to the same service is often successful again. There is <br>> also a <br>> > counter component who log the failing calls, once a service endpoints <br>> keeps <br>> > failing serveral times it will be marked as "permanently unavailable" <br>> and a <br>> > process-wide endpoint replacement will be executed, after this all <br>> > subsequent process instances will follow the updated BPEL with <br>> updated <br>> > endpoints (in the deployment descriptor). <br>> > <br>> > > If for some reason you cannot model the error handling in your BPEL <br>> > > process (which would be my first choice), it sounds like you would <br>> be <br>> > > better off capturing that logic elsewhere and using a fixed <br>> endpoint from <br>> > > BPEL. You could hide your 'real', potentially changing endpoints <br>> behind <br>> > > some other routing component (e.g. a camel route if you were <br>> running in <br>> > > servicemix). <br>> > <br>> > Using a routing component sounds interesting, although I don't want <br>> to <br>> > bloat the project with yet another component. But I will look into <br>> that <br>> > solution. Thank you! <br>> > <br>> > Best Regards, <br>> > <br>> > Thuy <br>> > <br>> > <br>> > > -----Original Message----- <br>> > > From: Greg Lucas [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=3" target="_top" rel="nofollow">greg.lucas@...</a>] <br>> > > Sent: Tuesday, December 15, 2009 8:12 PM <br>> > > To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=4" target="_top" rel="nofollow">dev@...</a> <br>> > > Subject: Re: Extend InstanceManagement API to provide endpoint <br>> > > manipulation <br>> > > <br>> > > Thuy, <br>> > > <br>> > > I'm not aware of any existing support for this. I'm not sure I <br>> fully <br>> > > understand the requirements though. If the intent is to redirect a <br>> > > failed <br>> > > invocation to another endpoint then modifying the endpoint for an <br>> > > active <br>> > > process instance seems insufficient. Wouldn't you also need to <br>> detect <br>> > > the <br>> > > failure and retry the failed activity? Would you also want all <br>> > > subsequent <br>> > > process instances to use the new endpoint, or would you expect each <br>> new <br>> > > instance to try the original ep and fail over as well? <br>> > > <br>> > > If for some reason you cannot model the error handling in your BPEL <br>> > > process (which would be my first choice), it sounds like you would <br>> be <br>> > > better off capturing that logic elsewhere and using a fixed <br>> endpoint <br>> > > from <br>> > > BPEL. You could hide your 'real', potentially changing endpoints <br>> behind <br>> > > some other routing component (e.g. a camel route if you were <br>> running in <br>> > > servicemix). <br>> > > <br>> > > ~Greg <br>> > > <br>> > > <br>> > > <br>> > > On Tue, 15 Dec 2009 11:16:00 -0500, Song Thuy Nguyen <br>> > > <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=5" target="_top" rel="nofollow">programming@...</a>> wrote: <br>> > > <br>> > > > Hi everyone, <br>> > > > <br>> > > > <br>> > > > I'm quite new to Apache ODE and mailing lists, hoping for your <br>> help. <br>> > > I <br>> > > > have <br>> > > > posted a similiar question in the user mailing list, but maybe <br>> here <br>> > > is a <br>> > > > better place to ask, as it has something to do with extending <br>> ODE. <br>> > > > <br>> > > > <br>> > > > As the title says I'm looking for a way to change service <br>> endpoints <br>> > > for <br>> > > > BPEL <br>> > > > process instances at runtime. That means that only one instance <br>> > > should be <br>> > > > affected by these changes, not the entire process and the <br>> deployment <br>> > > > descriptor. By convention of the project I'm working on, it is <br>> not <br>> > > > allowed <br>> > > > to write a BPEL-process that looks up service endpoints at a <br>> registry <br>> > > > service, put it in an  variable and use it as the dynamic <br>> endpoint. <br>> > > The <br>> > > > reason is we want to provide a fault resistant BPEL process <br>> execution <br>> > > by <br>> > > > replacing failing or unavailabe service endpoints by working ones <br>> > > with <br>> > > > transparency to the process. So there should be no sign of the <br>> "fault <br>> > > > handling" in the BPEL file. Failing services will be detected by <br>> a <br>> > > > monitor <br>> > > > component, but this is not my part. <br>> > > > <br>> > > > <br>> > > > I have tried to look into the Management API doc for processes <br>> and <br>> > > > instances <br>> > > > to find a method that can provide a solution, but I had no luck. <br>> > > There <br>> > > > are <br>> > > > only methods to get and set endpoints on a process-wide level, on <br>> a <br>> > > > instance <br>> > > > level however, those methods are not available. <br>> > > > <br>> > > > <br>> > > > It seems to me that the only way to get such a functionality is <br>> to <br>> > > extend <br>> > > > the Instance Management API and write those methods myself. If <br>> this <br>> > > is <br>> > > > right, can someone please tell me where to start? I think there <br>> > > should be <br>> > > > Java objects representing each BPEL instance, and there are <br>> variables <br>> > > > storing the endpoints, so if I change them, I would get the <br>> > > > functionality I <br>> > > > need , right? <br>> > > > <br>> > > > <br>> > > > Or maybe there is already a built-in mechanism to do that but I <br>> > > missed <br>> > > > it? <br>> > > > <br>> > > > <br>> > > > Any help or comment would be appreciated. <br>> > > <br>> > > __________ Information from ESET NOD32 Antivirus, version of virus <br>> > > signature database 4690 (20091215) __________ <br>> > > <br>> > > The message was checked by ESET NOD32 Antivirus. <br>> > > <br>> > > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > > <br>> > > <br>> > > <br>> > > <br>> > > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> Version <br>> > > 4634 (20091124) __________ <br>> > > <br>> > > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > > <br>> > > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > > <br>> > > <br>> > > <br>> > > <br>> > > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> Version <br>> > > 4634 (20091124) __________ <br>> > > <br>> > > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > > <br>> > > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > > <br>> > <br>> > <br>> <br>> <br>> -- <br>> Milinda Pathirage <br>> Senior Software Engineer & Product Manager WSO2 BPS; <br>> <a href="http://wso2.org/bps" target="_top" rel="nofollow">http://wso2.org/bps</a><br>> WSO2 Inc.; <a href="http://wso2.com" target="_top" rel="nofollow">http://wso2.com</a><br>> E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=6" target="_top" rel="nofollow">milinda@...</a>, <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26810130&i=7" target="_top" rel="nofollow">milinda.pathirage@...</a> <br>> Web: <a href="http://mpathirage.com" target="_top" rel="nofollow">http://mpathirage.com</a><br>> Blog: <a href="http://blog.mpathirage.com" target="_top" rel="nofollow">http://blog.mpathirage.com</a></div><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26809996 RE: Changing Endpoints of a Process Instance at RUNTIME 2009-12-16T03:55:25Z 2009-12-16T03:55:25Z BA Hello, <br>Thanks for pointing out where to start looking and extending ODE. That's roughly what I'm looking for. I will let you know if I succeed. <br>Any additional hints and ideas would still be appreciated! <br><br>Best regards, <br><br><br>Thuy <br><div class='shrinkable-quote'><br>> -----Original Message----- <br>> From: Tammo van Lessen [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=0" target="_top" rel="nofollow">tvanlessen@...</a>] <br>> Sent: Tuesday, December 15, 2009 10:40 PM <br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=1" target="_top" rel="nofollow">user@...</a> <br>> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>> <br>> Hi, <br>> <br>> As an academic I'd also go with slightly extending ODE. The Instance <br>> Management API is definitely a good starting point for that, I'd start <br>> with adding a new method to <br>> org.apache.ode.bpel.pmapi.InstanceManagement <br>> and implement it in <br>> org.apache.ode.bpel.engine.ProcessAndInstanceManagementImpl. The code <br>> for modifying the EPR of a partner link can be derived from ASSIGN <br>> and/or AssignHelper. <br>> <br>> HTH, <br>>   Tammo <br>> <br>> On 15.12.2009 21:46, Song Thuy Nguyen wrote: <br>> > Setting up a proxy is seen as one of the less desireable solution, <br>> because it would create a single point of failure. Incase the proxy <br>> component fails, the whole BPEL engine will stop working. Our system <br>> (as it is designed) as mentioned uses normal BPEL files without any <br>> dynamic binding capability, so it would also work if the proces <br>> instance rebinding component (which I'm trying to implement) fails. The <br>> system then would run like a normal BPEL engine without fault <br>> compensation ability. <br>> > I will look into the WS-Policy, maybe this will work for me, thank <br>> you! <br>> > <br>> > If anyone has another idea, especially how to extend ODE itself like <br>> in my first post, please let me know. <br>> > <br>> > Best regards, <br>> > <br>> > Thuy <br>> > <br>> > <br>> >> -----Original Message----- <br>> >> From: Ford, Mark - 0661 - MITLL [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=2" target="_top" rel="nofollow">mark.ford@...</a>] <br>> >> Sent: Tuesday, December 15, 2009 8:18 PM <br>> >> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=3" target="_top" rel="nofollow">user@...</a> <br>> >> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>> >> <br>> >> Have you considered setting up a proxy service that would handle <br>> >> retries or address rewriting? This would keep your BPEL simple since <br>> >> all of the changes are external to the BPEL and in fact external to <br>> >> ODE. Another option would be to modify the invoke layer for ODE to <br>> >> provide this behavior keyed off of WS-Policy. For a sample <br>> >> implementation of this policy, check out the docs here: <br>> >> <a href="http://tinyurl.com/ya4tmsk" target="_top" rel="nofollow">http://tinyurl.com/ya4tmsk</a><br>> >> <br>> >> <br>> >> <br>> >> On Dec 15, 2009, at 10:51 AM, Song Thuy Nguyen wrote: <br>> >> <br>> >>> Hi Marco, <br>> >>> Thanks for the fast answer and your suggestion, but the 2 links you <br>> >>> gave me <br>> >>> are not suitable for this problem. I read all the user manual of <br>> >>> apache ode <br>> >>> on the website before but didn't find any solution. The first link <br>> >>> describes <br>> >>> HOW endpoints can be represented, and the second one, as far as I <br>> >>> understand <br>> >>> describe is a way to manipulate endpoints on a process-wide level, <br>> >>> and there <br>> >>> is also a second problem with this solution (copied from <br>> >>> <a href="http://ode.apache.org/endpoint-configuration.html):" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html):</a><br>> >>> <br>> >>> " Dynamic refresh <br>> >>> <br>> >>> Properties are dynamically loaded and refreshed at run time. <br>> >>> The timing is the following: <br>> >>> On every request, if the file has not been polled during the last <br>> 30 <br>> >>> seconds <br>> >>> then check the file for updates. If any, reload it. <br>> >>> <br>> >>> Consequently, if you have updated properties, you have to wait ~30 <br>> >>> seconds <br>> >>> and then trigger a request." <br>> >>> <br>> >>> so you have to wait up to 30s to see the changes taking effect. <br>> >> That's <br>> >>> "ages" considering you are stopping a running instance to replace <br>> an <br>> >>> endpoint and continue. <br>> >>> <br>> >>> Looks like the 3rd suggestion is the only way to go. I'll let you <br>> >>> know if I <br>> >>> find an applicable concrete solution. <br>> >>> <br>> >>> Is there someone else with another solution for me? :) <br>> >>> <br>> >>> Regards, <br>> >>> <br>> >>> Thuy <br>> >>> <br>> >>> <br>> >>> <br>> >>> <br>> >>> -----Ursprüngliche Nachricht----- <br>> >>> Von: Marco Indaco [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=4" target="_top" rel="nofollow">marco.indaco@...</a>] <br>> >>> Gesendet: Dienstag, 15. Dezember 2009 14:52 <br>> >>> An: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=5" target="_top" rel="nofollow">user@...</a> <br>> >>> Betreff: Re: Changing Endpoints of a Process Instance at RUNTIME <br>> >>> <br>> >>> Hi song, <br>> >>> i'am working on your own objective, in my research project. <br>> >>> There are many solution that you can investigate. <br>> >>> <br>> >>> 1) <a href="http://ode.apache.org/endpoint-references.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-references.html</a>  see that link <br>> >>> <br>> >>> 2)Create, if monitor observes, for example, that a service is down, <br>> a <br>> >>> file .endpoint located in conf directory in Apache Ode. see that <br>> link <br>> >>> <a href="http://ode.apache.org/endpoint-configuration.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html</a><br>> >>> <br>> >>> 3) A more intrusive operation for modify source code to added these <br>> >>> functionalites <br>> >>> <br>> >>> If you are any idea please contact me...working together is <br>> powerful. <br>> >>> <br>> >>> Hi, for any question ask me!!! <br>> >>> <br>> >>> 2009/12/15 Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809996&i=6" target="_top" rel="nofollow">programming@...</a>>: <br>> >>>> Hi everyone, <br>> >>>> <br>> >>>> <br>> >>>> <br>> >>>> I'm quite new to Apache ODE and mailing lists, hoping for your <br>> help. <br>> >>>> <br>> >>>> As the title says I'm looking for a way to change service <br>> endpoints <br>> >>>> for <br>> >>> BPEL <br>> >>>> process instances at runtime. That means that only one instance <br>> >>>> should be <br>> >>>> affected by these changes, not the entire process and the <br>> deployment <br>> >>>> descriptor. By convention of the project I'm working on, it is not <br>> >>>> allowed <br>> >>>> to write a BPEL-process that looks up service endpoints at a <br>> >> registry <br>> >>>> service, put it in an  variable and use it as the dynamic <br>> endpoint. <br>> >>>> The <br>> >>>> reason is we want to provide a fault resistant BPEL process <br>> >>>> execution by <br>> >>>> replacing failing or unavailabe service endpoints by working ones <br>> >>>> with <br>> >>>> transparency to the process. So there should be no sign of the <br>> >> "fault <br>> >>>> handling" in the BPEL file. Failing services will be detected by a <br>> >>>> monitor <br>> >>>> component, but this is not my part. <br>> >>>> <br>> >>>> I have tried to look into the Management API for processes and <br>> >>>> instances <br>> >>> to <br>> >>>> find a method that can provide a solution, but I had no luck. <br>> There <br>> >>>> are <br>> >>> only <br>> >>>> methods to get and set endpoints on a process-wide level, on a <br>> >>>> instance <br>> >>>> level however, those methods are not available. <br>> >>>> <br>> >>>> It seems to me that the only way to get such a functionality is to <br>> >>>> extend <br>> >>>> the Instance Management API and write those methods myself, If <br>> this <br>> >>>> is <br>> >>>> right, can someone please tell me where to start? Any help would <br>> be <br>> >>>> appreciated. <br>> >>>> <br>> >>>> <br>> >>>> <br>> >>>> Thank you in advance <br>> >>>> <br>> >>>> <br>> >>>> <br>> >>>> Thuy <br>> >>>> <br>> >>>> <br>> >>> <br>> >>> __________ Information from ESET NOD32 Antivirus, version of virus <br>> >>> signature <br>> >>> database 4689 (20091215) __________ <br>> >>> <br>> >>> The message was checked by ESET NOD32 Antivirus. <br>> >>> <br>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> >>> <br>> >>> <br>> >>> <br>> >>> <br>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> >>> Version 4634 <br>> >>> (20091124) __________ <br>> >>> <br>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> >>> <br>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> >>> <br>> >>> <br>> >>> <br>> >>> <br>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> >>> Version 4634 <br>> >>> (20091124) __________ <br>> >>> <br>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> >>> <br>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> >>> <br>> >>> <br>> >>> <br>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> >>> Version 4634 <br>> >>> (20091124) __________ <br>> >>> <br>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> >>> <br>> >>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> >>> <br>> >>> <br>> >> <br>> >> <br>> >> <br>> >> <br>> >> -- <br>> >> Mark Ford <br>> >> MIT Lincoln Laboratory <br>> >> 244 Wood Street <br>> >> Lexington MA 02420 <br>> >> (781) 981-1843 <br>> > <br>> > <br>> <br>> <br>> -- <br>> Tammo van Lessen - <a href="http://www.taval.de" target="_top" rel="nofollow">http://www.taval.de</a></div><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26809806 Re: Callback to a process 2009-12-16T03:35:53Z 2009-12-16T03:35:53Z dawg I'm sure I need an extra partner link, and so I did add another port type to the process wsdl which should be mapped to the receive activity. As for the rest, I'm not sure I understand how that works. What does "initiate correlation set" mean? If I'm basing my correlation to the process instance by instance id which is a part of the callback message, it means that all other activities have nothing really to bind to the correlation set, so I'm not sure what would attaching correlation set to this activities do. <br>Another question is how would I "initialise" the correlation set with the process id so that when it has to be matched later with the callback part, it would be able to. <br><br>Given the following example simple workflow attached with a receive1 which activates the workflow, invoking some activity on a web service and returning the result, with parallel receive for receiving the callback, how can I configure the correlation such that messages having the part process id equals the process instance id will join the running instance rather than create a new one? <br><br><a href="http://old.nabble.com/file/p26809806/Picture%2B2.png" target="_top">Picture+2.png</a><br><br>I created a property called process id: <br><br><vprop:property name="processId" type="xsd:string"/> <br><br>and added a alias for the callback message part: <br><br><vprop:propertyAlias messageType="tns:MediaCompositeFaultCallbackOperationRequest" part="pid" propertyName="tns:processId"/> <br><br>But that surely is not enough. For one thing there needs to be a way to say that I want to match the incoming message part process id with a variable from the process. Another thing is what must be done with regards to correlation for the rest of the invoke/receive activities. <br><br>Thanks, <br>Dawg <br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color"> <div class="quote-author" style="font-weight: bold;">Greg Lucas-3 wrote:</div> <div class="quote-message shrinkable-quote">Sorry, hit send by mistake. <br><br>You will need a partner link for the receive, but it does not have to be a   <br>partner link used elsewhere in the process. You will also need to initiate   <br>the correlation set prior to the async receive; but you can do that on a   <br>message activity associated with a different partner link. For example,   <br>you might initiate the correlation set on the receive activity that   <br>instantiates the process instance, or on some invocation of another   <br>partner link that happens before entering the scope with your async   <br>receive. <br><br><br>~Greg <br><br>On Tue, 15 Dec 2009 16:00:03 -0500, Greg Lucas <greg.lucas@gmail.com>   <br>wrote: <br><br>> For this to work you'll need: <br>>   - a partner link for the receive activbity <br>> <br>> <br>> <br>> On Tue, 15 Dec 2009 15:07:05 -0500, dawg <zohar.etzioni@gmail.com> wrote: <br>> <br>>> <br>>> Hi, <br>>> <br>>> Here's what I'm trying to do: <br>>> In parallel to the whole execution flow of the process, I want to have <br>>> another receive activity that would be able to receive a message. Now   <br>>> the <br>>> match between the process to select and the message sent can be based   <br>>> on the <br>>> process id, so it is reasonable to assume that the sender has it. This   <br>>> is <br>>> the use case (or its vague version). <br>>> <br>>> I thought I'd be able to implement that with correlation sets, but I'm   <br>>> not <br>>> sure that's correct. The problem is that this callback message is not   <br>>> sent <br>>> from any of the partner links, and has no direct relation to any invoke <br>>> activity. So what I really want is that every other message that is   <br>>> directed <br>>> to this process will create a new instance, while this message will be <br>>> directed to the process which has this process id. <br>>> <br>>> Assuming I created a property process Id, and created an alias to it   <br>>> from <br>>> the message part that matches the callback message, and defined and   <br>>> attached <br>>> the correlation set to this callback receive activity. How do I   <br>>> initialise <br>>> the process id to match with? why do I have to attach the correlation   <br>>> set <br>>> (if I do) to all invoke/receive activities? <br>>> <br>>> Perhaps correlation sets are not the right solution to my problem. In   <br>>> that <br>>> case, any other ideas? </div> </div></blockquote> <p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26809030 [jira] Updated: (ODE-738) OpenJPA based DAO doesn't support wildcards properly in "name" and "namespace" filters in InstanceManagement 2009-12-16T02:23:20Z 2009-12-16T02:23:20Z JIRA jira@apache.org <br>     [ <a href="https://issues.apache.org/jira/browse/ODE-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ] <br><br>Waruna Ranasinghe updated ODE-738: <br>---------------------------------- <br><br>    Attachment: ODE-738.patch <br><br>This patch make possible to filter name and namespace using following style <br><br>He*l* <br><a href="http://ode/unit-s*le/H*" target="_top" rel="nofollow">http://ode/unit-s*le/H*</a><br><br><br>Additionally, instanceQueryCount mathod is added to get the instance count, for a interested party. Otherwise all the instances should be retrieved from the database   in order to get the count of the instances. Since both instanceQuery and instanceQueryCount have the same SQL generation, the SQL generation logic is moved to genSQL private method. <br><div class='shrinkable-quote'><br>> OpenJPA based DAO doesn't support  wildcards properly in "name" and "namespace" filters in InstanceManagement <br>> ------------------------------------------------------------------------------------------------------------- <br>> <br>>                 Key: ODE-738 <br>>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-738" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-738</a><br>>             Project: ODE <br>>          Issue Type: Bug <br>>          Components: Management API <br>>    Affects Versions: 2.0 <br>>            Reporter: Waruna Ranasinghe <br>>         Attachments: ODE-738.patch <br>> <br>> <br>> if we give the following strings as the namespace, it will not work properly <br>>           <br>> <a href="http://ode/unit-sample/H*" target="_top" rel="nofollow">http://ode/unit-sample/H*</a><br>> <a href="http://ode/unit-s*le/H*" target="_top" rel="nofollow">http://ode/unit-s*le/H*</a></div><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26806569 [jira] Created: (ODE-738) OpenJPA based DAO doesn't support wildcards properly in "name" and "namespace" filters in InstanceManagement 2009-12-15T21:46:18Z 2009-12-15T21:46:18Z JIRA jira@apache.org OpenJPA based DAO doesn't support  wildcards properly in "name" and "namespace" filters in InstanceManagement <br>------------------------------------------------------------------------------------------------------------- <br><br>                 Key: ODE-738 <br>                 URL: <a href="https://issues.apache.org/jira/browse/ODE-738" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/ODE-738</a><br>             Project: ODE <br>          Issue Type: Bug <br>          Components: Management API <br>    Affects Versions: 2.0 <br>            Reporter: Waruna Ranasinghe <br><br><br>if we give the following strings as the namespace, it will not work properly <br>          <br><a href="http://ode/unit-sample/H*" target="_top" rel="nofollow">http://ode/unit-sample/H*</a><br><a href="http://ode/unit-s*le/H*" target="_top" rel="nofollow">http://ode/unit-s*le/H*</a><br><br>-- <br>This message is automatically generated by JIRA. <br>- <br>You can reply to this email to add a comment to the issue online. <br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26805928 Re: Extend InstanceManagement API to provide endpoint manipulation 2009-12-15T19:51:45Z 2009-12-15T19:51:45Z Milinda Pathirage I also think that calling the service through a ESB will be a better <br>alternative your approach. In this way you can use ESB to handle fail-over <br>and failure handling is transparent to your BPEL. I think changing instance <br>at runtime is not a good solution for this scenario. You can use Apache <br>Synapse to handle fail-over. Please look endpoint section of article at[1]. <br><br>Thanks <br>Milinda <br><br>[1] <a href="http://wso2.org/library/2559" target="_top" rel="nofollow">http://wso2.org/library/2559</a><br><br>On Wed, Dec 16, 2009 at 2:01 AM, Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=0" target="_top" rel="nofollow">programming@...</a>>wrote: <br><div class='shrinkable-quote'><br>> Hello Greg, <br>> <br>> > Wouldn't you also need to detect the <br>> > failure and retry the failed activity? Would you also want all subsequent <br>> > process instances to use the new endpoint, or would you expect each new <br>> > instance to try the original ep and fail over as well? <br>> <br>> Once there is a failure calling a service endpoint, the process instance <br>> execution will be paused, the new endpoint will be written over the old ones <br>> and the processinstance will then be continued trying to call the last <br>> action (new calling for the new endpoint). This solution is a kind of <br>> "optimistic aproach" where service unavailability is mostly temporaly and <br>> the next call to the same service is often successful again. There is also a <br>> counter component who log the failing calls, once a service endpoints keeps <br>> failing serveral times it will be marked as "permanently unavailable" and a <br>> process-wide endpoint replacement will be executed, after this all <br>> subsequent process instances will follow the updated BPEL with updated <br>> endpoints (in the deployment descriptor). <br>> <br>> > If for some reason you cannot model the error handling in your BPEL <br>> > process (which would be my first choice), it sounds like you would be <br>> > better off capturing that logic elsewhere and using a fixed endpoint from <br>> > BPEL. You could hide your 'real', potentially changing endpoints behind <br>> > some other routing component (e.g. a camel route if you were running in <br>> > servicemix). <br>> <br>> Using a routing component sounds interesting, although I don't want to <br>> bloat the project with yet another component. But I will look into that <br>> solution. Thank you! <br>> <br>> Best Regards, <br>> <br>> Thuy <br>> <br>> <br>> > -----Original Message----- <br>> > From: Greg Lucas [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=1" target="_top" rel="nofollow">greg.lucas@...</a>] <br>> > Sent: Tuesday, December 15, 2009 8:12 PM <br>> > To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=2" target="_top" rel="nofollow">dev@...</a> <br>> > Subject: Re: Extend InstanceManagement API to provide endpoint <br>> > manipulation <br>> > <br>> > Thuy, <br>> > <br>> > I'm not aware of any existing support for this. I'm not sure I fully <br>> > understand the requirements though. If the intent is to redirect a <br>> > failed <br>> > invocation to another endpoint then modifying the endpoint for an <br>> > active <br>> > process instance seems insufficient. Wouldn't you also need to detect <br>> > the <br>> > failure and retry the failed activity? Would you also want all <br>> > subsequent <br>> > process instances to use the new endpoint, or would you expect each new <br>> > instance to try the original ep and fail over as well? <br>> > <br>> > If for some reason you cannot model the error handling in your BPEL <br>> > process (which would be my first choice), it sounds like you would be <br>> > better off capturing that logic elsewhere and using a fixed endpoint <br>> > from <br>> > BPEL. You could hide your 'real', potentially changing endpoints behind <br>> > some other routing component (e.g. a camel route if you were running in <br>> > servicemix). <br>> > <br>> > ~Greg <br>> > <br>> > <br>> > <br>> > On Tue, 15 Dec 2009 11:16:00 -0500, Song Thuy Nguyen <br>> > <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=3" target="_top" rel="nofollow">programming@...</a>> wrote: <br>> > <br>> > > Hi everyone, <br>> > > <br>> > > <br>> > > I'm quite new to Apache ODE and mailing lists, hoping for your help. <br>> > I <br>> > > have <br>> > > posted a similiar question in the user mailing list, but maybe here <br>> > is a <br>> > > better place to ask, as it has something to do with extending ODE. <br>> > > <br>> > > <br>> > > As the title says I'm looking for a way to change service endpoints <br>> > for <br>> > > BPEL <br>> > > process instances at runtime. That means that only one instance <br>> > should be <br>> > > affected by these changes, not the entire process and the deployment <br>> > > descriptor. By convention of the project I'm working on, it is not <br>> > > allowed <br>> > > to write a BPEL-process that looks up service endpoints at a registry <br>> > > service, put it in an  variable and use it as the dynamic endpoint. <br>> > The <br>> > > reason is we want to provide a fault resistant BPEL process execution <br>> > by <br>> > > replacing failing or unavailabe service endpoints by working ones <br>> > with <br>> > > transparency to the process. So there should be no sign of the "fault <br>> > > handling" in the BPEL file. Failing services will be detected by a <br>> > > monitor <br>> > > component, but this is not my part. <br>> > > <br>> > > <br>> > > I have tried to look into the Management API doc for processes and <br>> > > instances <br>> > > to find a method that can provide a solution, but I had no luck. <br>> > There <br>> > > are <br>> > > only methods to get and set endpoints on a process-wide level, on a <br>> > > instance <br>> > > level however, those methods are not available. <br>> > > <br>> > > <br>> > > It seems to me that the only way to get such a functionality is to <br>> > extend <br>> > > the Instance Management API and write those methods myself. If this <br>> > is <br>> > > right, can someone please tell me where to start? I think there <br>> > should be <br>> > > Java objects representing each BPEL instance, and there are variables <br>> > > storing the endpoints, so if I change them, I would get the <br>> > > functionality I <br>> > > need , right? <br>> > > <br>> > > <br>> > > Or maybe there is already a built-in mechanism to do that but I <br>> > missed <br>> > > it? <br>> > > <br>> > > <br>> > > Any help or comment would be appreciated. <br>> > <br>> > __________ Information from ESET NOD32 Antivirus, version of virus <br>> > signature database 4690 (20091215) __________ <br>> > <br>> > The message was checked by ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> > <br>> > <br>> > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version <br>> > 4634 (20091124) __________ <br>> > <br>> > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> > <br>> > <br>> > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version <br>> > 4634 (20091124) __________ <br>> > <br>> > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> <br>> </div><br><br>-- <br>Milinda Pathirage <br>Senior Software Engineer & Product Manager WSO2 BPS; <a href="http://wso2.org/bps" target="_top" rel="nofollow">http://wso2.org/bps</a><br>WSO2 Inc.; <a href="http://wso2.com" target="_top" rel="nofollow">http://wso2.com</a><br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=4" target="_top" rel="nofollow">milinda@...</a>, <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26805928&i=5" target="_top" rel="nofollow">milinda.pathirage@...</a> <br>Web: <a href="http://mpathirage.com" target="_top" rel="nofollow">http://mpathirage.com</a><br>Blog: <a href="http://blog.mpathirage.com" target="_top" rel="nofollow">http://blog.mpathirage.com</a><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-Dev-f16256.html" embed="fixTarget[16256]" target="_top" >Apache Ode Dev</a></p> tag:old.nabble.com,2006:post-26802251 Re: Changing Endpoints of a Process Instance at RUNTIME 2009-12-15T13:39:37Z 2009-12-15T13:39:37Z Tammo van Lessen Hi, <br><br>As an academic I'd also go with slightly extending ODE. The Instance <br>Management API is definitely a good starting point for that, I'd start <br>with adding a new method to org.apache.ode.bpel.pmapi.InstanceManagement <br>and implement it in <br>org.apache.ode.bpel.engine.ProcessAndInstanceManagementImpl. The code <br>for modifying the EPR of a partner link can be derived from ASSIGN <br>and/or AssignHelper. <br><br>HTH, <br>  Tammo <br><br>On 15.12.2009 21:46, Song Thuy Nguyen wrote: <div class='shrinkable-quote'><br>> Setting up a proxy is seen as one of the less desireable solution, because it would create a single point of failure. Incase the proxy component fails, the whole BPEL engine will stop working. Our system (as it is designed) as mentioned uses normal BPEL files without any dynamic binding capability, so it would also work if the proces instance rebinding component (which I'm trying to implement) fails. The system then would run like a normal BPEL engine without fault compensation ability. <br>> I will look into the WS-Policy, maybe this will work for me, thank you! <br>> <br>> If anyone has another idea, especially how to extend ODE itself like in my first post, please let me know. <br>> <br>> Best regards, <br>> <br>> Thuy <br>> <br>> <br>>> -----Original Message----- <br>>> From: Ford, Mark - 0661 - MITLL [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802251&i=0" target="_top" rel="nofollow">mark.ford@...</a>] <br>>> Sent: Tuesday, December 15, 2009 8:18 PM <br>>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802251&i=1" target="_top" rel="nofollow">user@...</a> <br>>> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>>> <br>>> Have you considered setting up a proxy service that would handle <br>>> retries or address rewriting? This would keep your BPEL simple since <br>>> all of the changes are external to the BPEL and in fact external to <br>>> ODE. Another option would be to modify the invoke layer for ODE to <br>>> provide this behavior keyed off of WS-Policy. For a sample <br>>> implementation of this policy, check out the docs here: <br>>> <a href="http://tinyurl.com/ya4tmsk" target="_top" rel="nofollow">http://tinyurl.com/ya4tmsk</a><br>>> <br>>> <br>>> <br>>> On Dec 15, 2009, at 10:51 AM, Song Thuy Nguyen wrote: <br>>> <br>>>> Hi Marco, <br>>>> Thanks for the fast answer and your suggestion, but the 2 links you <br>>>> gave me <br>>>> are not suitable for this problem. I read all the user manual of <br>>>> apache ode <br>>>> on the website before but didn't find any solution. The first link <br>>>> describes <br>>>> HOW endpoints can be represented, and the second one, as far as I <br>>>> understand <br>>>> describe is a way to manipulate endpoints on a process-wide level, <br>>>> and there <br>>>> is also a second problem with this solution (copied from <br>>>> <a href="http://ode.apache.org/endpoint-configuration.html):" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html):</a><br>>>> <br>>>> " Dynamic refresh <br>>>> <br>>>> Properties are dynamically loaded and refreshed at run time. <br>>>> The timing is the following: <br>>>> On every request, if the file has not been polled during the last 30 <br>>>> seconds <br>>>> then check the file for updates. If any, reload it. <br>>>> <br>>>> Consequently, if you have updated properties, you have to wait ~30 <br>>>> seconds <br>>>> and then trigger a request." <br>>>> <br>>>> so you have to wait up to 30s to see the changes taking effect. <br>>> That's <br>>>> "ages" considering you are stopping a running instance to replace an <br>>>> endpoint and continue. <br>>>> <br>>>> Looks like the 3rd suggestion is the only way to go. I'll let you <br>>>> know if I <br>>>> find an applicable concrete solution. <br>>>> <br>>>> Is there someone else with another solution for me? :) <br>>>> <br>>>> Regards, <br>>>> <br>>>> Thuy <br>>>> <br>>>> <br>>>> <br>>>> <br>>>> -----Ursprüngliche Nachricht----- <br>>>> Von: Marco Indaco [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802251&i=2" target="_top" rel="nofollow">marco.indaco@...</a>] <br>>>> Gesendet: Dienstag, 15. Dezember 2009 14:52 <br>>>> An: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802251&i=3" target="_top" rel="nofollow">user@...</a> <br>>>> Betreff: Re: Changing Endpoints of a Process Instance at RUNTIME <br>>>> <br>>>> Hi song, <br>>>> i'am working on your own objective, in my research project. <br>>>> There are many solution that you can investigate. <br>>>> <br>>>> 1) <a href="http://ode.apache.org/endpoint-references.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-references.html</a>  see that link <br>>>> <br>>>> 2)Create, if monitor observes, for example, that a service is down, a <br>>>> file .endpoint located in conf directory in Apache Ode. see that link <br>>>> <a href="http://ode.apache.org/endpoint-configuration.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html</a><br>>>> <br>>>> 3) A more intrusive operation for modify source code to added these <br>>>> functionalites <br>>>> <br>>>> If you are any idea please contact me...working together is powerful. <br>>>> <br>>>> Hi, for any question ask me!!! <br>>>> <br>>>> 2009/12/15 Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802251&i=4" target="_top" rel="nofollow">programming@...</a>>: <br>>>>> Hi everyone, <br>>>>> <br>>>>> <br>>>>> <br>>>>> I'm quite new to Apache ODE and mailing lists, hoping for your help. <br>>>>> <br>>>>> As the title says I'm looking for a way to change service endpoints <br>>>>> for <br>>>> BPEL <br>>>>> process instances at runtime. That means that only one instance <br>>>>> should be <br>>>>> affected by these changes, not the entire process and the deployment <br>>>>> descriptor. By convention of the project I'm working on, it is not <br>>>>> allowed <br>>>>> to write a BPEL-process that looks up service endpoints at a <br>>> registry <br>>>>> service, put it in an  variable and use it as the dynamic endpoint. <br>>>>> The <br>>>>> reason is we want to provide a fault resistant BPEL process <br>>>>> execution by <br>>>>> replacing failing or unavailabe service endpoints by working ones <br>>>>> with <br>>>>> transparency to the process. So there should be no sign of the <br>>> "fault <br>>>>> handling" in the BPEL file. Failing services will be detected by a <br>>>>> monitor <br>>>>> component, but this is not my part. <br>>>>> <br>>>>> I have tried to look into the Management API for processes and <br>>>>> instances <br>>>> to <br>>>>> find a method that can provide a solution, but I had no luck. There <br>>>>> are <br>>>> only <br>>>>> methods to get and set endpoints on a process-wide level, on a <br>>>>> instance <br>>>>> level however, those methods are not available. <br>>>>> <br>>>>> It seems to me that the only way to get such a functionality is to <br>>>>> extend <br>>>>> the Instance Management API and write those methods myself, If this <br>>>>> is <br>>>>> right, can someone please tell me where to start? Any help would be <br>>>>> appreciated. <br>>>>> <br>>>>> <br>>>>> <br>>>>> Thank you in advance <br>>>>> <br>>>>> <br>>>>> <br>>>>> Thuy <br>>>>> <br>>>>> <br>>>> <br>>>> __________ Information from ESET NOD32 Antivirus, version of virus <br>>>> signature <br>>>> database 4689 (20091215) __________ <br>>>> <br>>>> The message was checked by ESET NOD32 Antivirus. <br>>>> <br>>>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>>> <br>>>> <br>>>> <br>>>> <br>>>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>>> Version 4634 <br>>>> (20091124) __________ <br>>>> <br>>>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>>> <br>>>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>>> <br>>>> <br>>>> <br>>>> <br>>>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>>> Version 4634 <br>>>> (20091124) __________ <br>>>> <br>>>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>>> <br>>>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>>> <br>>>> <br>>>> <br>>>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>>>> Version 4634 <br>>>> (20091124) __________ <br>>>> <br>>>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>>>> <br>>>> <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>>>> <br>>>> <br>>> <br>>> <br>>> <br>>> <br>>> -- <br>>> Mark Ford <br>>> MIT Lincoln Laboratory <br>>> 244 Wood Street <br>>> Lexington MA 02420 <br>>> (781) 981-1843 <br>> <br>> </div><br><br>-- <br>Tammo van Lessen - <a href="http://www.taval.de" target="_top" rel="nofollow">http://www.taval.de</a><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26801847 Re: Callback to a process 2009-12-15T13:10:48Z 2009-12-15T13:10:48Z Greg Lucas-3 Sorry, hit send by mistake. <br><br>You will need a partner link for the receive, but it does not have to be a   <br>partner link used elsewhere in the process. You will also need to initiate   <br>the correlation set prior to the async receive; but you can do that on a   <br>message activity associated with a different partner link. For example,   <br>you might initiate the correlation set on the receive activity that   <br>instantiates the process instance, or on some invocation of another   <br>partner link that happens before entering the scope with your async   <br>receive. <br><br><br>~Greg <br><br>On Tue, 15 Dec 2009 16:00:03 -0500, Greg Lucas <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801847&i=0" target="_top" rel="nofollow">greg.lucas@...</a>>   <br>wrote: <br><div class='shrinkable-quote'><br>> For this to work you'll need: <br>>   - a partner link for the receive activbity <br>> <br>> <br>> <br>> On Tue, 15 Dec 2009 15:07:05 -0500, dawg <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801847&i=1" target="_top" rel="nofollow">zohar.etzioni@...</a>> wrote: <br>> <br>>> <br>>> Hi, <br>>> <br>>> Here's what I'm trying to do: <br>>> In parallel to the whole execution flow of the process, I want to have <br>>> another receive activity that would be able to receive a message. Now   <br>>> the <br>>> match between the process to select and the message sent can be based   <br>>> on the <br>>> process id, so it is reasonable to assume that the sender has it. This   <br>>> is <br>>> the use case (or its vague version). <br>>> <br>>> I thought I'd be able to implement that with correlation sets, but I'm   <br>>> not <br>>> sure that's correct. The problem is that this callback message is not   <br>>> sent <br>>> from any of the partner links, and has no direct relation to any invoke <br>>> activity. So what I really want is that every other message that is   <br>>> directed <br>>> to this process will create a new instance, while this message will be <br>>> directed to the process which has this process id. <br>>> <br>>> Assuming I created a property process Id, and created an alias to it   <br>>> from <br>>> the message part that matches the callback message, and defined and   <br>>> attached <br>>> the correlation set to this callback receive activity. How do I   <br>>> initialise <br>>> the process id to match with? why do I have to attach the correlation   <br>>> set <br>>> (if I do) to all invoke/receive activities? <br>>> <br>>> Perhaps correlation sets are not the right solution to my problem. In   <br>>> that <br>>> case, any other ideas? <br></div><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26801691 Re: Callback to a process 2009-12-15T13:00:03Z 2009-12-15T13:00:03Z Greg Lucas-3 For this to work you'll need: <br>  - a partner link for the receive activbity <br><br><br><br>On Tue, 15 Dec 2009 15:07:05 -0500, dawg <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801691&i=0" target="_top" rel="nofollow">zohar.etzioni@...</a>> wrote: <br><div class='shrinkable-quote'><br>> <br>> Hi, <br>> <br>> Here's what I'm trying to do: <br>> In parallel to the whole execution flow of the process, I want to have <br>> another receive activity that would be able to receive a message. Now the <br>> match between the process to select and the message sent can be based on   <br>> the <br>> process id, so it is reasonable to assume that the sender has it. This is <br>> the use case (or its vague version). <br>> <br>> I thought I'd be able to implement that with correlation sets, but I'm   <br>> not <br>> sure that's correct. The problem is that this callback message is not   <br>> sent <br>> from any of the partner links, and has no direct relation to any invoke <br>> activity. So what I really want is that every other message that is   <br>> directed <br>> to this process will create a new instance, while this message will be <br>> directed to the process which has this process id. <br>> <br>> Assuming I created a property process Id, and created an alias to it from <br>> the message part that matches the callback message, and defined and   <br>> attached <br>> the correlation set to this callback receive activity. How do I   <br>> initialise <br>> the process id to match with? why do I have to attach the correlation set <br>> (if I do) to all invoke/receive activities? <br>> <br>> Perhaps correlation sets are not the right solution to my problem. In   <br>> that <br>> case, any other ideas? <br>> <br>> Thanks, <br>> Dawg </div><br><br>-- <br>Greg Lucas <br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p> tag:old.nabble.com,2006:post-26801498 RE: Changing Endpoints of a Process Instance at RUNTIME 2009-12-15T12:46:08Z 2009-12-15T12:46:08Z BA Setting up a proxy is seen as one of the less desireable solution, because it would create a single point of failure. Incase the proxy component fails, the whole BPEL engine will stop working. Our system (as it is designed) as mentioned uses normal BPEL files without any dynamic binding capability, so it would also work if the proces instance rebinding component (which I'm trying to implement) fails. The system then would run like a normal BPEL engine without fault compensation ability. <br>I will look into the WS-Policy, maybe this will work for me, thank you! <br><br>If anyone has another idea, especially how to extend ODE itself like in my first post, please let me know. <br><br>Best regards, <br><br>Thuy <br><br><div class='shrinkable-quote'><br>> -----Original Message----- <br>> From: Ford, Mark - 0661 - MITLL [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801498&i=0" target="_top" rel="nofollow">mark.ford@...</a>] <br>> Sent: Tuesday, December 15, 2009 8:18 PM <br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801498&i=1" target="_top" rel="nofollow">user@...</a> <br>> Subject: Re: Changing Endpoints of a Process Instance at RUNTIME <br>> <br>> Have you considered setting up a proxy service that would handle <br>> retries or address rewriting? This would keep your BPEL simple since <br>> all of the changes are external to the BPEL and in fact external to <br>> ODE. Another option would be to modify the invoke layer for ODE to <br>> provide this behavior keyed off of WS-Policy. For a sample <br>> implementation of this policy, check out the docs here: <br>> <a href="http://tinyurl.com/ya4tmsk" target="_top" rel="nofollow">http://tinyurl.com/ya4tmsk</a><br>> <br>> <br>> <br>> On Dec 15, 2009, at 10:51 AM, Song Thuy Nguyen wrote: <br>> <br>> > Hi Marco, <br>> > Thanks for the fast answer and your suggestion, but the 2 links you <br>> > gave me <br>> > are not suitable for this problem. I read all the user manual of <br>> > apache ode <br>> > on the website before but didn't find any solution. The first link <br>> > describes <br>> > HOW endpoints can be represented, and the second one, as far as I <br>> > understand <br>> > describe is a way to manipulate endpoints on a process-wide level, <br>> > and there <br>> > is also a second problem with this solution (copied from <br>> > <a href="http://ode.apache.org/endpoint-configuration.html):" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html):</a><br>> > <br>> > " Dynamic refresh <br>> > <br>> > Properties are dynamically loaded and refreshed at run time. <br>> > The timing is the following: <br>> > On every request, if the file has not been polled during the last 30 <br>> > seconds <br>> > then check the file for updates. If any, reload it. <br>> > <br>> > Consequently, if you have updated properties, you have to wait ~30 <br>> > seconds <br>> > and then trigger a request." <br>> > <br>> > so you have to wait up to 30s to see the changes taking effect. <br>> That's <br>> > "ages" considering you are stopping a running instance to replace an <br>> > endpoint and continue. <br>> > <br>> > Looks like the 3rd suggestion is the only way to go. I'll let you <br>> > know if I <br>> > find an applicable concrete solution. <br>> > <br>> > Is there someone else with another solution for me? :) <br>> > <br>> > Regards, <br>> > <br>> > Thuy <br>> > <br>> > <br>> > <br>> > <br>> > -----Ursprüngliche Nachricht----- <br>> > Von: Marco Indaco [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801498&i=2" target="_top" rel="nofollow">marco.indaco@...</a>] <br>> > Gesendet: Dienstag, 15. Dezember 2009 14:52 <br>> > An: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801498&i=3" target="_top" rel="nofollow">user@...</a> <br>> > Betreff: Re: Changing Endpoints of a Process Instance at RUNTIME <br>> > <br>> > Hi song, <br>> > i'am working on your own objective, in my research project. <br>> > There are many solution that you can investigate. <br>> > <br>> > 1) <a href="http://ode.apache.org/endpoint-references.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-references.html</a>  see that link <br>> > <br>> > 2)Create, if monitor observes, for example, that a service is down, a <br>> > file .endpoint located in conf directory in Apache Ode. see that link <br>> > <a href="http://ode.apache.org/endpoint-configuration.html" target="_top" rel="nofollow">http://ode.apache.org/endpoint-configuration.html</a><br>> > <br>> > 3) A more intrusive operation for modify source code to added these <br>> > functionalites <br>> > <br>> > If you are any idea please contact me...working together is powerful. <br>> > <br>> > Hi, for any question ask me!!! <br>> > <br>> > 2009/12/15 Song Thuy Nguyen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26801498&i=4" target="_top" rel="nofollow">programming@...</a>>: <br>> >> Hi everyone, <br>> >> <br>> >> <br>> >> <br>> >> I'm quite new to Apache ODE and mailing lists, hoping for your help. <br>> >> <br>> >> As the title says I'm looking for a way to change service endpoints <br>> >> for <br>> > BPEL <br>> >> process instances at runtime. That means that only one instance <br>> >> should be <br>> >> affected by these changes, not the entire process and the deployment <br>> >> descriptor. By convention of the project I'm working on, it is not <br>> >> allowed <br>> >> to write a BPEL-process that looks up service endpoints at a <br>> registry <br>> >> service, put it in an  variable and use it as the dynamic endpoint. <br>> >> The <br>> >> reason is we want to provide a fault resistant BPEL process <br>> >> execution by <br>> >> replacing failing or unavailabe service endpoints by working ones <br>> >> with <br>> >> transparency to the process. So there should be no sign of the <br>> "fault <br>> >> handling" in the BPEL file. Failing services will be detected by a <br>> >> monitor <br>> >> component, but this is not my part. <br>> >> <br>> >> I have tried to look into the Management API for processes and <br>> >> instances <br>> > to <br>> >> find a method that can provide a solution, but I had no luck. There <br>> >> are <br>> > only <br>> >> methods to get and set endpoints on a process-wide level, on a <br>> >> instance <br>> >> level however, those methods are not available. <br>> >> <br>> >> It seems to me that the only way to get such a functionality is to <br>> >> extend <br>> >> the Instance Management API and write those methods myself, If this <br>> >> is <br>> >> right, can someone please tell me where to start? Any help would be <br>> >> appreciated. <br>> >> <br>> >> <br>> >> <br>> >> Thank you in advance <br>> >> <br>> >> <br>> >> <br>> >> Thuy <br>> >> <br>> >> <br>> > <br>> > __________ Information from ESET NOD32 Antivirus, version of virus <br>> > signature <br>> > database 4689 (20091215) __________ <br>> > <br>> > The message was checked by ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> > <br>> > <br>> > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> > Version 4634 <br>> > (20091124) __________ <br>> > <br>> > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> > <br>> > <br>> > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> > Version 4634 <br>> > (20091124) __________ <br>> > <br>> > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> > <br>> > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank- <br>> > Version 4634 <br>> > (20091124) __________ <br>> > <br>> > E-Mail wurde geprüft mit ESET NOD32 Antivirus. <br>> > <br>> > <a href="http://www.eset.com" target="_top" rel="nofollow">http://www.eset.com</a><br>> > <br>> > <br>> <br>> <br>> <br>> <br>> -- <br>> Mark Ford <br>> MIT Lincoln Laboratory <br>> 244 Wood Street <br>> Lexington MA 02420 <br>> (781) 981-1843 </div><br><br><p>From forum: <a href="http://old.nabble.com/Apache-Ode-User-f16255.html" embed="fixTarget[16255]" target="_top" >Apache Ode User</a></p>