You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Ciaran Jessup (JIRA)" <ji...@apache.org> on 2009/05/12 17:47:45 UTC
[jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
*MY* dynamic endpoint references have suddenly stopped working :(
-----------------------------------------------------------------
Key: ODE-601
URL: https://issues.apache.org/jira/browse/ODE-601
Project: ODE
Issue Type: Bug
Affects Versions: 1.3.2, 1.3.3
Environment: n/a
Reporter: Ciaran Jessup
My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
<!-- in the bpel:variables section -->
<bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
<!--- Trying to invoke a service call -->
<bpel:assign name="proxyPreparation">
<bpel:copy>
<bpel:from>
<bpel:literal>
<wsa:EndpointReference xmlns:swsdl="uri:swsdl">
<wsa:Address />
<wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
</wsa:EndpointReference>
</bpel:literal>
</bpel:from>
<bpel:to variable="DynamicEndpointRef" />
</bpel:copy>
<bpel:copy>
<bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
<bpel:to variable="ProxyAddress" />
</bpel:copy>
<bpel:copy>
<bpel:from variable="ProxyAddress" />
<bpel:to variable="DynamicEndpointRef">
<bpel:query>wsa:Address</bpel:query>
</bpel:to>
</bpel:copy>
<bpel:copy>
<bpel:from variable="DynamicEndpointRef" />
<bpel:to partnerLink="PPS" />
</bpel:copy>
<bpel:copy>
<bpel:from>
<bpel:literal>
<swsdl:PPI>
<swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
</swsdl:PPI>
</bpel:literal>
</bpel:from>
<bpel:to variable="ppIn" part="parameters" />
</bpel:copy>
</bpel:assign>
<bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
And when the flow executes I see an error along the lines of :
ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
<service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
<Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
<wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
</service-ref>
I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
A request such as :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
<soapenv:Header/>
<soapenv:Body>
<wor:ExecuteWorkflow>
<wor:userCredentials>
<smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
<smf:applicationName>NA</smf:applicationName>
</wor:userCredentials>
<wor:workItem version="54">
<smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
</wor:workItem>
</wor:ExecuteWorkflow>
</soapenv:Body>
</soapenv:Envelope>
Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
Hi Karthick,
Please accept my apologies, not quite sure how but the wrong XSD was in that
zip file, I've corrected the error and re-attached it to the JIRA. I'm
grateful for you finding the time to look at the issue and very apologetic
that what I gave you was useless :(
With regards to a simpler test case, this *is* my simple test case :),
because I'm not sure whether its something I'm doing wrong I've had to leave
in all the core things I'm doing in my flow, I have stripped down all the
Complex types to the bare minimum that I can get away with and removed any
un-neccessary fluff from the BPEL (for example I've removed all the fault
handling code etc.)
Many thanks
- Cj.
On Wed, May 20, 2009 at 12:16 AM, Karthick Sankarachary <
sankarachary@intalio.com> wrote:
> Ciaran,
>
> There appears to be something missing in the project that you attached to
> ODE-601, because I can't quite deploy it:
>
> 16:12:32,865 ERROR [DeploymentPoller] Deployment of InboundGateway-1
> failed,
> aborting for now.
> org.apache.ode.bpel.iapi.ContextException: Deploy failed; error:
> [CompilationErrors] Compilation completed with 3 error(s):
> ...var/processes/InboundGateway-1/InboundGateway.wsdl:0: error:
> [SchemaError] Error in schema processing: src-resolve: Cannot resolve the
> name 'Platform' to a(n) 'type definition' component.
> .../var/processes/InboundGateway-1/proxy.wsdl:0: error:
> [SchemaError] Error in schema processing: src-resolve: Cannot resolve the
> name 'NamedAuditableObject' to a(n) 'type definition' component.
> ...var/processes/InboundGateway-1/proxy.wsdl:0: error: [SchemaError]
> Error in schema processing: src-resolve: Cannot resolve the name
> 'NamedAuditableObject' to a(n) 'type definition' component.
>
> Can you come up with a simpler test case that works if at all possible?
>
> Regards,
> Karthick
>
> On 5/19/09, Ciaran <ci...@gmail.com> wrote:
> >
> > Wowser, thanks for the update :)
> > -cj.
> >
> > On Tue, May 19, 2009 at 11:30 PM, Alex Boisvert <boisvert@intalio.com
> > >wrote:
> >
> >
> > > Speaking for the Intalio crew, we've been swamped in work recently
> > putting
> > > Apache Ode and other technologies in the clouds...
> > >
> > > http://www.intalio.com/news/blog-posts/mad-rush/
> > >
> > >
> >
> http://www.intalio.com/news/press-releases/intalio-acquires-bpm-and-crm-companies-launches-intalio-cloud/
> > >
> > > We'll get back to your issue soon after we land back on terra firma.
> > >
> > > alex
> > >
> > >
> > > On Tue, May 19, 2009 at 2:58 AM, Ciaran <ci...@gmail.com> wrote:
> > >
> > > > I would really appreciate some feedback, just anything really on this
> > > issue
> > > > I *cannot* use ODE currently, and I would rather like to given the
> time
> > > > I've
> > > > invested in investigating the memory issues previously :(
> > > >
> > > > Many thanks.
> > > > -cj.
> > > >
> > > >
> > > > On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
> > > >
> > > > > Hi Folks,Has anyone had a chance to look at this issue at all? I
> > still
> > > > > cannot use ODE with this issue in the code (or in my BPEL wherever
> > the
> > > > fault
> > > > > is), which is a shame :(
> > > > > -cj.
> > > > >
> > > > >
> > > > > On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <
> > jira@apache.org
> > > > >wrote:
> > > > >
> > > > >> *MY* dynamic endpoint references have suddenly stopped working :(
> > > > >> -----------------------------------------------------------------
> > > > >>
> > > > >> Key: ODE-601
> > > > >> URL:
> https://issues.apache.org/jira/browse/ODE-601
> > > > >> Project: ODE
> > > > >> Issue Type: Bug
> > > > >> Affects Versions: 1.3.2, 1.3.3
> > > > >> Environment: n/a
> > > > >> Reporter: Ciaran Jessup
> > > > >>
> > > > >>
> > > > >> My BPEL flows (I *think*, although its possible this hasn't been
> > > > function
> > > > >> as expected) used to work before changeset [765432] (on the ODE
> > 1_XXX
> > > > >> branch), they no longer do (and continue to work when I rever that
> > > > changeset
> > > > >> out.
> > > > >> I think its something to do with the 'location' property now being
> > set
> > > > on
> > > > >> the variable reference where it previously wasn't, but I'm very
> very
> > > out
> > > > of
> > > > >> depth. I've attached what I think is the relevant snipped of BPEL
> > > that
> > > > I'm
> > > > >> using for doing my invoke:
> > > > >>
> > > > >> <!-- in the bpel:variables section -->
> > > > >> <bpel:variable name="DynamicEndpointRef"
> > > element="wsa:EndpointReference"
> > > > >> />
> > > > >>
> > > > >>
> > > > >> <!--- Trying to invoke a service call -->
> > > > >> <bpel:assign name="proxyPreparation">
> > > > >> <bpel:copy>
> > > > >> <bpel:from>
> > > > >> <bpel:literal>
> > > > >> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> > > > >> <wsa:Address />
> > > > >> <wsa:ServiceName
> > PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > > > >> </wsa:EndpointReference>
> > > > >> </bpel:literal>
> > > > >> </bpel:from>
> > > > >> <bpel:to variable="DynamicEndpointRef" />
> > > > >> </bpel:copy>
> > > > >> <bpel:copy>
> > > > >>
> > > > >>
> > > >
> >
> > >
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> > > > >> <bpel:to variable="ProxyAddress" />
> > > > >> </bpel:copy>
> > > > >> <bpel:copy>
> > > > >> <bpel:from variable="ProxyAddress" />
> > > > >> <bpel:to variable="DynamicEndpointRef">
> > > > >> <bpel:query>wsa:Address</bpel:query>
> > > > >> </bpel:to>
> > > > >> </bpel:copy>
> > > > >> <bpel:copy>
> > > > >> <bpel:from variable="DynamicEndpointRef" />
> > > > >> <bpel:to partnerLink="PPS" />
> > > > >> </bpel:copy>
> > > > >> <bpel:copy>
> > > > >> <bpel:from>
> > > > >> <bpel:literal>
> > > > >> <swsdl:PPI>
> > > > >>
> > > > >>
> > >
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> > > > >> </swsdl:PPI>
> > > > >> </bpel:literal>
> > > > >> </bpel:from>
> > > > >> <bpel:to variable="ppIn" part="parameters" />
> > > > >> </bpel:copy>
> > > > >> </bpel:assign>
> > > > >> <bpel:invoke name="InvokePPS" partnerLink="PPS"
> > > portType="swsdl:PPSSoap"
> > > > >> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> > > > >>
> > > > >>
> > > > >> And when the flow executes I see an error along the lines of :
> > > > >>
> > > > >> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for
> partner
> > > EPR
> > > > >> <?xml version="1.0" encoding="UTF-8"?>
> > > > >> <service-ref xmlns="
> > http://docs.oasis-open.org/wsbpel/2.0/serviceref
> > > ">
> > > > >> <Address xmlns="
> > > > >> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> > > > >> http://server/myaddress.asmx?wsdl</Address>
> > > > >> <wsa:ServiceName xmlns:wsa="
> > > > >> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> > > > >> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > > > >> </service-ref>
> > > > >>
> > > > >> I do not get this error, and the correct web service seems to get
> > > called
> > > > >> when I revert the change.. any ideas, is my BPEL flawed, or has an
> > > issue
> > > > >> been introduced?
> > > > >>
> > > > >>
> > > > >> Please find attached a fully deployed process, this will require
> you
> > > to
> > > > >> mock a service that adheres to the wsdl in proxy.wsdl.
> > > > >>
> > > > >> A request such as :
> > > > >> <soapenv:Envelope xmlns:soapenv="
> > > > >> http://schemas.xmlsoap.org/soap/envelope/"
> > > > >> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> > > > >> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> > > > >> <soapenv:Header/>
> > > > >> <soapenv:Body>
> > > > >> <wor:ExecuteWorkflow>
> > > > >> <wor:userCredentials>
> > > > >>
> > > <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> > > > >> <smf:applicationName>NA</smf:applicationName>
> > > > >> </wor:userCredentials>
> > > > >> <wor:workItem version="54">
> > > >
> > >> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> > > > >> </wor:workItem>
> > > > >> </wor:ExecuteWorkflow>
> > > > >> </soapenv:Body>
> > > > >> </soapenv:Envelope>
> > > > >>
> > > > >> Will cause the error to occur on trunk head, but the error won't
> > occur
> > > > if
> > > > >> you revert changeset [765432] I do believe its to dow with the
> > > dynamic
> > > > >> addressing breaking the partnerlink stuff, but I'm not clever
> enough
> > > to
> > > > pin
> > > > >> it down :(
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> This message is automatically generated by JIRA.
> > > > >> -
> > > > >> You can reply to this email to add a comment to the issue online.
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Best Regards,
> Karthick Sankarachary
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Karthick Sankarachary <sa...@intalio.com>.
Ciaran,
There appears to be something missing in the project that you attached to
ODE-601, because I can't quite deploy it:
16:12:32,865 ERROR [DeploymentPoller] Deployment of InboundGateway-1 failed,
aborting for now.
org.apache.ode.bpel.iapi.ContextException: Deploy failed; error:
[CompilationErrors] Compilation completed with 3 error(s):
...var/processes/InboundGateway-1/InboundGateway.wsdl:0: error:
[SchemaError] Error in schema processing: src-resolve: Cannot resolve the
name 'Platform' to a(n) 'type definition' component.
.../var/processes/InboundGateway-1/proxy.wsdl:0: error:
[SchemaError] Error in schema processing: src-resolve: Cannot resolve the
name 'NamedAuditableObject' to a(n) 'type definition' component.
...var/processes/InboundGateway-1/proxy.wsdl:0: error: [SchemaError]
Error in schema processing: src-resolve: Cannot resolve the name
'NamedAuditableObject' to a(n) 'type definition' component.
Can you come up with a simpler test case that works if at all possible?
Regards,
Karthick
On 5/19/09, Ciaran <ci...@gmail.com> wrote:
>
> Wowser, thanks for the update :)
> -cj.
>
> On Tue, May 19, 2009 at 11:30 PM, Alex Boisvert <boisvert@intalio.com
> >wrote:
>
>
> > Speaking for the Intalio crew, we've been swamped in work recently
> putting
> > Apache Ode and other technologies in the clouds...
> >
> > http://www.intalio.com/news/blog-posts/mad-rush/
> >
> >
> http://www.intalio.com/news/press-releases/intalio-acquires-bpm-and-crm-companies-launches-intalio-cloud/
> >
> > We'll get back to your issue soon after we land back on terra firma.
> >
> > alex
> >
> >
> > On Tue, May 19, 2009 at 2:58 AM, Ciaran <ci...@gmail.com> wrote:
> >
> > > I would really appreciate some feedback, just anything really on this
> > issue
> > > I *cannot* use ODE currently, and I would rather like to given the time
> > > I've
> > > invested in investigating the memory issues previously :(
> > >
> > > Many thanks.
> > > -cj.
> > >
> > >
> > > On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
> > >
> > > > Hi Folks,Has anyone had a chance to look at this issue at all? I
> still
> > > > cannot use ODE with this issue in the code (or in my BPEL wherever
> the
> > > fault
> > > > is), which is a shame :(
> > > > -cj.
> > > >
> > > >
> > > > On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <
> jira@apache.org
> > > >wrote:
> > > >
> > > >> *MY* dynamic endpoint references have suddenly stopped working :(
> > > >> -----------------------------------------------------------------
> > > >>
> > > >> Key: ODE-601
> > > >> URL: https://issues.apache.org/jira/browse/ODE-601
> > > >> Project: ODE
> > > >> Issue Type: Bug
> > > >> Affects Versions: 1.3.2, 1.3.3
> > > >> Environment: n/a
> > > >> Reporter: Ciaran Jessup
> > > >>
> > > >>
> > > >> My BPEL flows (I *think*, although its possible this hasn't been
> > > function
> > > >> as expected) used to work before changeset [765432] (on the ODE
> 1_XXX
> > > >> branch), they no longer do (and continue to work when I rever that
> > > changeset
> > > >> out.
> > > >> I think its something to do with the 'location' property now being
> set
> > > on
> > > >> the variable reference where it previously wasn't, but I'm very very
> > out
> > > of
> > > >> depth. I've attached what I think is the relevant snipped of BPEL
> > that
> > > I'm
> > > >> using for doing my invoke:
> > > >>
> > > >> <!-- in the bpel:variables section -->
> > > >> <bpel:variable name="DynamicEndpointRef"
> > element="wsa:EndpointReference"
> > > >> />
> > > >>
> > > >>
> > > >> <!--- Trying to invoke a service call -->
> > > >> <bpel:assign name="proxyPreparation">
> > > >> <bpel:copy>
> > > >> <bpel:from>
> > > >> <bpel:literal>
> > > >> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> > > >> <wsa:Address />
> > > >> <wsa:ServiceName
> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > > >> </wsa:EndpointReference>
> > > >> </bpel:literal>
> > > >> </bpel:from>
> > > >> <bpel:to variable="DynamicEndpointRef" />
> > > >> </bpel:copy>
> > > >> <bpel:copy>
> > > >>
> > > >>
> > >
>
> > <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> > > >> <bpel:to variable="ProxyAddress" />
> > > >> </bpel:copy>
> > > >> <bpel:copy>
> > > >> <bpel:from variable="ProxyAddress" />
> > > >> <bpel:to variable="DynamicEndpointRef">
> > > >> <bpel:query>wsa:Address</bpel:query>
> > > >> </bpel:to>
> > > >> </bpel:copy>
> > > >> <bpel:copy>
> > > >> <bpel:from variable="DynamicEndpointRef" />
> > > >> <bpel:to partnerLink="PPS" />
> > > >> </bpel:copy>
> > > >> <bpel:copy>
> > > >> <bpel:from>
> > > >> <bpel:literal>
> > > >> <swsdl:PPI>
> > > >>
> > > >>
> > <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> > > >> </swsdl:PPI>
> > > >> </bpel:literal>
> > > >> </bpel:from>
> > > >> <bpel:to variable="ppIn" part="parameters" />
> > > >> </bpel:copy>
> > > >> </bpel:assign>
> > > >> <bpel:invoke name="InvokePPS" partnerLink="PPS"
> > portType="swsdl:PPSSoap"
> > > >> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> > > >>
> > > >>
> > > >> And when the flow executes I see an error along the lines of :
> > > >>
> > > >> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner
> > EPR
> > > >> <?xml version="1.0" encoding="UTF-8"?>
> > > >> <service-ref xmlns="
> http://docs.oasis-open.org/wsbpel/2.0/serviceref
> > ">
> > > >> <Address xmlns="
> > > >> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> > > >> http://server/myaddress.asmx?wsdl</Address>
> > > >> <wsa:ServiceName xmlns:wsa="
> > > >> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> > > >> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > > >> </service-ref>
> > > >>
> > > >> I do not get this error, and the correct web service seems to get
> > called
> > > >> when I revert the change.. any ideas, is my BPEL flawed, or has an
> > issue
> > > >> been introduced?
> > > >>
> > > >>
> > > >> Please find attached a fully deployed process, this will require you
> > to
> > > >> mock a service that adheres to the wsdl in proxy.wsdl.
> > > >>
> > > >> A request such as :
> > > >> <soapenv:Envelope xmlns:soapenv="
> > > >> http://schemas.xmlsoap.org/soap/envelope/"
> > > >> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> > > >> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> > > >> <soapenv:Header/>
> > > >> <soapenv:Body>
> > > >> <wor:ExecuteWorkflow>
> > > >> <wor:userCredentials>
> > > >>
> > <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> > > >> <smf:applicationName>NA</smf:applicationName>
> > > >> </wor:userCredentials>
> > > >> <wor:workItem version="54">
> > >
> >> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> > > >> </wor:workItem>
> > > >> </wor:ExecuteWorkflow>
> > > >> </soapenv:Body>
> > > >> </soapenv:Envelope>
> > > >>
> > > >> Will cause the error to occur on trunk head, but the error won't
> occur
> > > if
> > > >> you revert changeset [765432] I do believe its to dow with the
> > dynamic
> > > >> addressing breaking the partnerlink stuff, but I'm not clever enough
> > to
> > > pin
> > > >> it down :(
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> This message is automatically generated by JIRA.
> > > >> -
> > > >> You can reply to this email to add a comment to the issue online.
> > > >>
> > > >>
> > > >
> > >
> >
>
--
Best Regards,
Karthick Sankarachary
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
Wowser, thanks for the update :)
-cj.
On Tue, May 19, 2009 at 11:30 PM, Alex Boisvert <bo...@intalio.com>wrote:
> Speaking for the Intalio crew, we've been swamped in work recently putting
> Apache Ode and other technologies in the clouds...
>
> http://www.intalio.com/news/blog-posts/mad-rush/
>
> http://www.intalio.com/news/press-releases/intalio-acquires-bpm-and-crm-companies-launches-intalio-cloud/
>
> We'll get back to your issue soon after we land back on terra firma.
>
> alex
>
>
> On Tue, May 19, 2009 at 2:58 AM, Ciaran <ci...@gmail.com> wrote:
>
> > I would really appreciate some feedback, just anything really on this
> issue
> > I *cannot* use ODE currently, and I would rather like to given the time
> > I've
> > invested in investigating the memory issues previously :(
> >
> > Many thanks.
> > -cj.
> >
> >
> > On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
> >
> > > Hi Folks,Has anyone had a chance to look at this issue at all? I still
> > > cannot use ODE with this issue in the code (or in my BPEL wherever the
> > fault
> > > is), which is a shame :(
> > > -cj.
> > >
> > >
> > > On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <jira@apache.org
> > >wrote:
> > >
> > >> *MY* dynamic endpoint references have suddenly stopped working :(
> > >> -----------------------------------------------------------------
> > >>
> > >> Key: ODE-601
> > >> URL: https://issues.apache.org/jira/browse/ODE-601
> > >> Project: ODE
> > >> Issue Type: Bug
> > >> Affects Versions: 1.3.2, 1.3.3
> > >> Environment: n/a
> > >> Reporter: Ciaran Jessup
> > >>
> > >>
> > >> My BPEL flows (I *think*, although its possible this hasn't been
> > function
> > >> as expected) used to work before changeset [765432] (on the ODE 1_XXX
> > >> branch), they no longer do (and continue to work when I rever that
> > changeset
> > >> out.
> > >> I think its something to do with the 'location' property now being set
> > on
> > >> the variable reference where it previously wasn't, but I'm very very
> out
> > of
> > >> depth. I've attached what I think is the relevant snipped of BPEL
> that
> > I'm
> > >> using for doing my invoke:
> > >>
> > >> <!-- in the bpel:variables section -->
> > >> <bpel:variable name="DynamicEndpointRef"
> element="wsa:EndpointReference"
> > >> />
> > >>
> > >>
> > >> <!--- Trying to invoke a service call -->
> > >> <bpel:assign name="proxyPreparation">
> > >> <bpel:copy>
> > >> <bpel:from>
> > >> <bpel:literal>
> > >> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> > >> <wsa:Address />
> > >> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > >> </wsa:EndpointReference>
> > >> </bpel:literal>
> > >> </bpel:from>
> > >> <bpel:to variable="DynamicEndpointRef" />
> > >> </bpel:copy>
> > >> <bpel:copy>
> > >>
> > >>
> >
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> > >> <bpel:to variable="ProxyAddress" />
> > >> </bpel:copy>
> > >> <bpel:copy>
> > >> <bpel:from variable="ProxyAddress" />
> > >> <bpel:to variable="DynamicEndpointRef">
> > >> <bpel:query>wsa:Address</bpel:query>
> > >> </bpel:to>
> > >> </bpel:copy>
> > >> <bpel:copy>
> > >> <bpel:from variable="DynamicEndpointRef" />
> > >> <bpel:to partnerLink="PPS" />
> > >> </bpel:copy>
> > >> <bpel:copy>
> > >> <bpel:from>
> > >> <bpel:literal>
> > >> <swsdl:PPI>
> > >>
> > >>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> > >> </swsdl:PPI>
> > >> </bpel:literal>
> > >> </bpel:from>
> > >> <bpel:to variable="ppIn" part="parameters" />
> > >> </bpel:copy>
> > >> </bpel:assign>
> > >> <bpel:invoke name="InvokePPS" partnerLink="PPS"
> portType="swsdl:PPSSoap"
> > >> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> > >>
> > >>
> > >> And when the flow executes I see an error along the lines of :
> > >>
> > >> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner
> EPR
> > >> <?xml version="1.0" encoding="UTF-8"?>
> > >> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref
> ">
> > >> <Address xmlns="
> > >> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> > >> http://server/myaddress.asmx?wsdl</Address>
> > >> <wsa:ServiceName xmlns:wsa="
> > >> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> > >> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> > >> </service-ref>
> > >>
> > >> I do not get this error, and the correct web service seems to get
> called
> > >> when I revert the change.. any ideas, is my BPEL flawed, or has an
> issue
> > >> been introduced?
> > >>
> > >>
> > >> Please find attached a fully deployed process, this will require you
> to
> > >> mock a service that adheres to the wsdl in proxy.wsdl.
> > >>
> > >> A request such as :
> > >> <soapenv:Envelope xmlns:soapenv="
> > >> http://schemas.xmlsoap.org/soap/envelope/"
> > >> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> > >> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> > >> <soapenv:Header/>
> > >> <soapenv:Body>
> > >> <wor:ExecuteWorkflow>
> > >> <wor:userCredentials>
> > >>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> > >> <smf:applicationName>NA</smf:applicationName>
> > >> </wor:userCredentials>
> > >> <wor:workItem version="54">
> > >> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> > >> </wor:workItem>
> > >> </wor:ExecuteWorkflow>
> > >> </soapenv:Body>
> > >> </soapenv:Envelope>
> > >>
> > >> Will cause the error to occur on trunk head, but the error won't occur
> > if
> > >> you revert changeset [765432] I do believe its to dow with the
> dynamic
> > >> addressing breaking the partnerlink stuff, but I'm not clever enough
> to
> > pin
> > >> it down :(
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> This message is automatically generated by JIRA.
> > >> -
> > >> You can reply to this email to add a comment to the issue online.
> > >>
> > >>
> > >
> >
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Alex Boisvert <bo...@intalio.com>.
Speaking for the Intalio crew, we've been swamped in work recently putting
Apache Ode and other technologies in the clouds...
http://www.intalio.com/news/blog-posts/mad-rush/
http://www.intalio.com/news/press-releases/intalio-acquires-bpm-and-crm-companies-launches-intalio-cloud/
We'll get back to your issue soon after we land back on terra firma.
alex
On Tue, May 19, 2009 at 2:58 AM, Ciaran <ci...@gmail.com> wrote:
> I would really appreciate some feedback, just anything really on this issue
> I *cannot* use ODE currently, and I would rather like to given the time
> I've
> invested in investigating the memory issues previously :(
>
> Many thanks.
> -cj.
>
>
> On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
>
> > Hi Folks,Has anyone had a chance to look at this issue at all? I still
> > cannot use ODE with this issue in the code (or in my BPEL wherever the
> fault
> > is), which is a shame :(
> > -cj.
> >
> >
> > On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <jira@apache.org
> >wrote:
> >
> >> *MY* dynamic endpoint references have suddenly stopped working :(
> >> -----------------------------------------------------------------
> >>
> >> Key: ODE-601
> >> URL: https://issues.apache.org/jira/browse/ODE-601
> >> Project: ODE
> >> Issue Type: Bug
> >> Affects Versions: 1.3.2, 1.3.3
> >> Environment: n/a
> >> Reporter: Ciaran Jessup
> >>
> >>
> >> My BPEL flows (I *think*, although its possible this hasn't been
> function
> >> as expected) used to work before changeset [765432] (on the ODE 1_XXX
> >> branch), they no longer do (and continue to work when I rever that
> changeset
> >> out.
> >> I think its something to do with the 'location' property now being set
> on
> >> the variable reference where it previously wasn't, but I'm very very out
> of
> >> depth. I've attached what I think is the relevant snipped of BPEL that
> I'm
> >> using for doing my invoke:
> >>
> >> <!-- in the bpel:variables section -->
> >> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference"
> >> />
> >>
> >>
> >> <!--- Trying to invoke a service call -->
> >> <bpel:assign name="proxyPreparation">
> >> <bpel:copy>
> >> <bpel:from>
> >> <bpel:literal>
> >> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> >> <wsa:Address />
> >> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> >> </wsa:EndpointReference>
> >> </bpel:literal>
> >> </bpel:from>
> >> <bpel:to variable="DynamicEndpointRef" />
> >> </bpel:copy>
> >> <bpel:copy>
> >>
> >>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> >> <bpel:to variable="ProxyAddress" />
> >> </bpel:copy>
> >> <bpel:copy>
> >> <bpel:from variable="ProxyAddress" />
> >> <bpel:to variable="DynamicEndpointRef">
> >> <bpel:query>wsa:Address</bpel:query>
> >> </bpel:to>
> >> </bpel:copy>
> >> <bpel:copy>
> >> <bpel:from variable="DynamicEndpointRef" />
> >> <bpel:to partnerLink="PPS" />
> >> </bpel:copy>
> >> <bpel:copy>
> >> <bpel:from>
> >> <bpel:literal>
> >> <swsdl:PPI>
> >>
> >> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> >> </swsdl:PPI>
> >> </bpel:literal>
> >> </bpel:from>
> >> <bpel:to variable="ppIn" part="parameters" />
> >> </bpel:copy>
> >> </bpel:assign>
> >> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap"
> >> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> >>
> >>
> >> And when the flow executes I see an error along the lines of :
> >>
> >> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> >> <Address xmlns="
> >> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> >> http://server/myaddress.asmx?wsdl</Address>
> >> <wsa:ServiceName xmlns:wsa="
> >> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> >> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> >> </service-ref>
> >>
> >> I do not get this error, and the correct web service seems to get called
> >> when I revert the change.. any ideas, is my BPEL flawed, or has an issue
> >> been introduced?
> >>
> >>
> >> Please find attached a fully deployed process, this will require you to
> >> mock a service that adheres to the wsdl in proxy.wsdl.
> >>
> >> A request such as :
> >> <soapenv:Envelope xmlns:soapenv="
> >> http://schemas.xmlsoap.org/soap/envelope/"
> >> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> >> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> >> <soapenv:Header/>
> >> <soapenv:Body>
> >> <wor:ExecuteWorkflow>
> >> <wor:userCredentials>
> >> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> >> <smf:applicationName>NA</smf:applicationName>
> >> </wor:userCredentials>
> >> <wor:workItem version="54">
> >> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> >> </wor:workItem>
> >> </wor:ExecuteWorkflow>
> >> </soapenv:Body>
> >> </soapenv:Envelope>
> >>
> >> Will cause the error to occur on trunk head, but the error won't occur
> if
> >> you revert changeset [765432] I do believe its to dow with the dynamic
> >> addressing breaking the partnerlink stuff, but I'm not clever enough to
> pin
> >> it down :(
> >>
> >>
> >>
> >>
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> You can reply to this email to add a comment to the issue online.
> >>
> >>
> >
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
I would really appreciate some feedback, just anything really on this issue
I *cannot* use ODE currently, and I would rather like to given the time I've
invested in investigating the memory issues previously :(
Many thanks.
-cj.
On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
> Hi Folks,Has anyone had a chance to look at this issue at all? I still
> cannot use ODE with this issue in the code (or in my BPEL wherever the fault
> is), which is a shame :(
> -cj.
>
>
> On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <ji...@apache.org>wrote:
>
>> *MY* dynamic endpoint references have suddenly stopped working :(
>> -----------------------------------------------------------------
>>
>> Key: ODE-601
>> URL: https://issues.apache.org/jira/browse/ODE-601
>> Project: ODE
>> Issue Type: Bug
>> Affects Versions: 1.3.2, 1.3.3
>> Environment: n/a
>> Reporter: Ciaran Jessup
>>
>>
>> My BPEL flows (I *think*, although its possible this hasn't been function
>> as expected) used to work before changeset [765432] (on the ODE 1_XXX
>> branch), they no longer do (and continue to work when I rever that changeset
>> out.
>> I think its something to do with the 'location' property now being set on
>> the variable reference where it previously wasn't, but I'm very very out of
>> depth. I've attached what I think is the relevant snipped of BPEL that I'm
>> using for doing my invoke:
>>
>> <!-- in the bpel:variables section -->
>> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference"
>> />
>>
>>
>> <!--- Trying to invoke a service call -->
>> <bpel:assign name="proxyPreparation">
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal>
>> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
>> <wsa:Address />
>> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
>> </wsa:EndpointReference>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="DynamicEndpointRef" />
>> </bpel:copy>
>> <bpel:copy>
>>
>> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
>> <bpel:to variable="ProxyAddress" />
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from variable="ProxyAddress" />
>> <bpel:to variable="DynamicEndpointRef">
>> <bpel:query>wsa:Address</bpel:query>
>> </bpel:to>
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from variable="DynamicEndpointRef" />
>> <bpel:to partnerLink="PPS" />
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal>
>> <swsdl:PPI>
>>
>> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
>> </swsdl:PPI>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="ppIn" part="parameters" />
>> </bpel:copy>
>> </bpel:assign>
>> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap"
>> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
>>
>>
>> And when the flow executes I see an error along the lines of :
>>
>> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR
>> <?xml version="1.0" encoding="UTF-8"?>
>> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
>> <Address xmlns="
>> http://schemas.xmlsoap.org/ws/2003/03/addressing">
>> http://server/myaddress.asmx?wsdl</Address>
>> <wsa:ServiceName xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2003/03/addressing"
>> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
>> </service-ref>
>>
>> I do not get this error, and the correct web service seems to get called
>> when I revert the change.. any ideas, is my BPEL flawed, or has an issue
>> been introduced?
>>
>>
>> Please find attached a fully deployed process, this will require you to
>> mock a service that adheres to the wsdl in proxy.wsdl.
>>
>> A request such as :
>> <soapenv:Envelope xmlns:soapenv="
>> http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
>> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
>> <soapenv:Header/>
>> <soapenv:Body>
>> <wor:ExecuteWorkflow>
>> <wor:userCredentials>
>> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
>> <smf:applicationName>NA</smf:applicationName>
>> </wor:userCredentials>
>> <wor:workItem version="54">
>> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
>> </wor:workItem>
>> </wor:ExecuteWorkflow>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> Will cause the error to occur on trunk head, but the error won't occur if
>> you revert changeset [765432] I do believe its to dow with the dynamic
>> addressing breaking the partnerlink stuff, but I'm not clever enough to pin
>> it down :(
>>
>>
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
I would really appreciate some feedback, just anything really on this issue
I *cannot* use ODE currently, and I would rather like to given the time I've
invested in investigating the memory issues previously :(
Many thanks.
-cj.
On Thu, May 14, 2009 at 8:27 PM, Ciaran <ci...@gmail.com> wrote:
> Hi Folks,Has anyone had a chance to look at this issue at all? I still
> cannot use ODE with this issue in the code (or in my BPEL wherever the fault
> is), which is a shame :(
> -cj.
>
>
> On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <ji...@apache.org>wrote:
>
>> *MY* dynamic endpoint references have suddenly stopped working :(
>> -----------------------------------------------------------------
>>
>> Key: ODE-601
>> URL: https://issues.apache.org/jira/browse/ODE-601
>> Project: ODE
>> Issue Type: Bug
>> Affects Versions: 1.3.2, 1.3.3
>> Environment: n/a
>> Reporter: Ciaran Jessup
>>
>>
>> My BPEL flows (I *think*, although its possible this hasn't been function
>> as expected) used to work before changeset [765432] (on the ODE 1_XXX
>> branch), they no longer do (and continue to work when I rever that changeset
>> out.
>> I think its something to do with the 'location' property now being set on
>> the variable reference where it previously wasn't, but I'm very very out of
>> depth. I've attached what I think is the relevant snipped of BPEL that I'm
>> using for doing my invoke:
>>
>> <!-- in the bpel:variables section -->
>> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference"
>> />
>>
>>
>> <!--- Trying to invoke a service call -->
>> <bpel:assign name="proxyPreparation">
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal>
>> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
>> <wsa:Address />
>> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
>> </wsa:EndpointReference>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="DynamicEndpointRef" />
>> </bpel:copy>
>> <bpel:copy>
>>
>> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
>> <bpel:to variable="ProxyAddress" />
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from variable="ProxyAddress" />
>> <bpel:to variable="DynamicEndpointRef">
>> <bpel:query>wsa:Address</bpel:query>
>> </bpel:to>
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from variable="DynamicEndpointRef" />
>> <bpel:to partnerLink="PPS" />
>> </bpel:copy>
>> <bpel:copy>
>> <bpel:from>
>> <bpel:literal>
>> <swsdl:PPI>
>>
>> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
>> </swsdl:PPI>
>> </bpel:literal>
>> </bpel:from>
>> <bpel:to variable="ppIn" part="parameters" />
>> </bpel:copy>
>> </bpel:assign>
>> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap"
>> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
>>
>>
>> And when the flow executes I see an error along the lines of :
>>
>> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR
>> <?xml version="1.0" encoding="UTF-8"?>
>> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
>> <Address xmlns="
>> http://schemas.xmlsoap.org/ws/2003/03/addressing">
>> http://server/myaddress.asmx?wsdl</Address>
>> <wsa:ServiceName xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2003/03/addressing"
>> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
>> </service-ref>
>>
>> I do not get this error, and the correct web service seems to get called
>> when I revert the change.. any ideas, is my BPEL flawed, or has an issue
>> been introduced?
>>
>>
>> Please find attached a fully deployed process, this will require you to
>> mock a service that adheres to the wsdl in proxy.wsdl.
>>
>> A request such as :
>> <soapenv:Envelope xmlns:soapenv="
>> http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
>> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
>> <soapenv:Header/>
>> <soapenv:Body>
>> <wor:ExecuteWorkflow>
>> <wor:userCredentials>
>> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
>> <smf:applicationName>NA</smf:applicationName>
>> </wor:userCredentials>
>> <wor:workItem version="54">
>> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
>> </wor:workItem>
>> </wor:ExecuteWorkflow>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> Will cause the error to occur on trunk head, but the error won't occur if
>> you revert changeset [765432] I do believe its to dow with the dynamic
>> addressing breaking the partnerlink stuff, but I'm not clever enough to pin
>> it down :(
>>
>>
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
Hi Folks,Has anyone had a chance to look at this issue at all? I still
cannot use ODE with this issue in the code (or in my BPEL wherever the fault
is), which is a shame :(
-cj.
On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <ji...@apache.org>wrote:
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function
> as expected) used to work before changeset [765432] (on the ODE 1_XXX
> branch), they no longer do (and continue to work when I rever that changeset
> out.
> I think its something to do with the 'location' property now being set on
> the variable reference where it previously wasn't, but I'm very very out of
> depth. I've attached what I think is the relevant snipped of BPEL that I'm
> using for doing my invoke:
>
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
>
>
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap"
> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
>
>
> And when the flow executes I see an error along the lines of :
>
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR
> <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="
> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="
> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
>
> I do not get this error, and the correct web service seems to get called
> when I revert the change.. any ideas, is my BPEL flawed, or has an issue
> been introduced?
>
>
> Please find attached a fully deployed process, this will require you to
> mock a service that adheres to the wsdl in proxy.wsdl.
>
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> "
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Will cause the error to occur on trunk head, but the error won't occur if
> you revert changeset [765432] I do believe its to dow with the dynamic
> addressing breaking the partnerlink stuff, but I'm not clever enough to pin
> it down :(
>
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Created: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by Ciaran <ci...@gmail.com>.
Hi Folks,Has anyone had a chance to look at this issue at all? I still
cannot use ODE with this issue in the code (or in my BPEL wherever the fault
is), which is a shame :(
-cj.
On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) <ji...@apache.org>wrote:
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function
> as expected) used to work before changeset [765432] (on the ODE 1_XXX
> branch), they no longer do (and continue to work when I rever that changeset
> out.
> I think its something to do with the 'location' property now being set on
> the variable reference where it previously wasn't, but I'm very very out of
> depth. I've attached what I think is the relevant snipped of BPEL that I'm
> using for doing my invoke:
>
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
>
>
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap"
> operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
>
>
> And when the flow executes I see an error along the lines of :
>
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR
> <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="
> http://schemas.xmlsoap.org/ws/2003/03/addressing">
> http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="
> http://schemas.xmlsoap.org/ws/2003/03/addressing"
> PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
>
> I do not get this error, and the correct web service seems to get called
> when I revert the change.. any ideas, is my BPEL flawed, or has an issue
> been introduced?
>
>
> Please find attached a fully deployed process, this will require you to
> mock a service that adheres to the wsdl in proxy.wsdl.
>
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> "
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Will cause the error to occur on trunk head, but the error won't occur if
> you revert changeset [765432] I do believe its to dow with the dynamic
> addressing breaking the partnerlink stuff, but I'm not clever enough to pin
> it down :(
>
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Updated: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthick Sankarachary updated ODE-601:
--------------------------------------
Summary: Cannot Assign Dynamic EPRs To Partner Links (was: *MY* dynamic endpoint references have suddenly stopped working :()
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-601:
------------------------------
Attachment: InboundGateway.zip
A full BPEL and all relevant dependencies that exhibits the described fault.
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Attachments: InboundGateway.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthick Sankarachary resolved ODE-601.
---------------------------------------
Resolution: Fixed
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-601:
------------------------------
Attachment: InboundGateway-13.zip
An example test (and now deployable) BPEL that exhibits the afore-mentioned issue.
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713969#action_12713969 ]
Ciaran Jessup commented on ODE-601:
-----------------------------------
Thanks Karthick,
I can confirm with your changes (and if I change the ws-addressing namespace I use) my BPEL now works with ODE. I take it there's no intention to support multiple WS Addressing versions then ? ... I'm puzzled as to how it seemed to work previously without the namespace change however , any ideas?
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by "Ian Harrigan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713347#action_12713347 ]
Ian Harrigan commented on ODE-601:
----------------------------------
Hi there - im getting the exact same issue as this. Is there a fix (or work around) available that doesnt involve reverting to an older version?
Ill investigate more tomorrow - if required i can post an example project to illustrate this issue. It seems like a pretty fundemental thing...
Cheers,
Ian Harrigan
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714096#action_12714096 ]
Karthick Sankarachary commented on ODE-601:
-------------------------------------------
That's a good question. I believe that was a case of two wrongs making a right. Even though your intention was to assign a <wsa:EndpointReference> to the partner link, it ended up assigning the value of the wsa:EndpointReference/wsa:Address instead. It so happens that the value is a valid URL endpoint, and is processed as such. Now, the engine does the right thing, which is to assign the <wsa:EndpointReference> itself to the partner link, provided, of course, that you are using the latest version of WS-Addressing.
To answer your question about WS-Addressing versions, we currently only support the latest version of WS-Addressing as specified here: http://www.w3.org/Submission/ws-addressing/. Do you have a good justification for using the older version over the latest one? If so, please file a request for enhancement that describes your use case.
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713769#action_12713769 ]
Karthick Sankarachary commented on ODE-601:
-------------------------------------------
It appears that there was a latent bug in the piece of code that handles assignments of dynamic EPRs to partner links, which apparently surfaced after revision 765432. I believe that that was the underlying cause of this issue, which has now been resolved (see revision 779324).
Ciaran, You may want to read our documentation on EPRs available here: http://cwiki.apache.org/ODExSITE/endpoint-references.html. In particular, note the namespace that we use for WS-Addressing, which is not the same as what your BPEL process assumes. Also, your BPEL project still tries to invoke your internal .NET service, so unfortunately, it still doesn't make for a good test case.
Regards,
Karthick
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-601:
------------------------------
Attachment: (was: InboundGateway.zip)
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ODE-601) *MY* dynamic endpoint references have
suddenly stopped working :(
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthick Sankarachary reassigned ODE-601:
-----------------------------------------
Assignee: Karthick Sankarachary
> *MY* dynamic endpoint references have suddenly stopped working :(
> -----------------------------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-601) Cannot Assign Dynamic EPRs To Partner
Links
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714114#action_12714114 ]
Ciaran Jessup commented on ODE-601:
-----------------------------------
Ah, I see, oddly this error also works in ActiveBPEL :) But I'm glad we uncovered the problem, and I'll remedy our BPEL generation code asap!
With regards to mulitple WS-Addressing styles, I don't believe I currently have a relevant use-case, it was more a point of interest :)
> Cannot Assign Dynamic EPRs To Partner Links
> -------------------------------------------
>
> Key: ODE-601
> URL: https://issues.apache.org/jira/browse/ODE-601
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3
> Environment: n/a
> Reporter: Ciaran Jessup
> Assignee: Karthick Sankarachary
> Attachments: InboundGateway-13.zip
>
>
> My BPEL flows (I *think*, although its possible this hasn't been function as expected) used to work before changeset [765432] (on the ODE 1_XXX branch), they no longer do (and continue to work when I rever that changeset out.
> I think its something to do with the 'location' property now being set on the variable reference where it previously wasn't, but I'm very very out of depth. I've attached what I think is the relevant snipped of BPEL that I'm using for doing my invoke:
> <!-- in the bpel:variables section -->
> <bpel:variable name="DynamicEndpointRef" element="wsa:EndpointReference" />
> <!--- Trying to invoke a service call -->
> <bpel:assign name="proxyPreparation">
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <wsa:EndpointReference xmlns:swsdl="uri:swsdl">
> <wsa:Address />
> <wsa:ServiceName PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </wsa:EndpointReference>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="DynamicEndpointRef" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>bpel:doXslTransform("GetNextAddress.xsl",$DynamicEndpointRef/wsa:Address)</bpel:from>
> <bpel:to variable="ProxyAddress" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="ProxyAddress" />
> <bpel:to variable="DynamicEndpointRef">
> <bpel:query>wsa:Address</bpel:query>
> </bpel:to>
> </bpel:copy>
> <bpel:copy>
> <bpel:from variable="DynamicEndpointRef" />
> <bpel:to partnerLink="PPS" />
> </bpel:copy>
> <bpel:copy>
> <bpel:from>
> <bpel:literal>
> <swsdl:PPI>
> <swsdl:processId>9f538fdb-ca36-4d5d-a056-d6bf92632f75</swsdl:processId>
> </swsdl:PPI>
> </bpel:literal>
> </bpel:from>
> <bpel:to variable="ppIn" part="parameters" />
> </bpel:copy>
> </bpel:assign>
> <bpel:invoke name="InvokePPS" partnerLink="PPS" portType="swsdl:PPSSoap" operation="PPI" inputVariable="ppIn" outputVariable="ppOut" />
> And when the flow executes I see an error along the lines of :
> ERROR - GeronimoLog.error(104) | Couldn't find endpoint for partner EPR <?xml version="1.0" encoding="UTF-8"?>
> <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref">
> <Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://server/myaddress.asmx?wsdl</Address>
> <wsa:ServiceName xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" PortName="PPSSoap">swsdl:PPS</wsa:ServiceName>
> </service-ref>
> I do not get this error, and the correct web service seems to get called when I revert the change.. any ideas, is my BPEL flawed, or has an issue been introduced?
> Please find attached a fully deployed process, this will require you to mock a service that adheres to the wsdl in proxy.wsdl.
> A request such as :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wor="http://www.myco.com/xml/sa/4.0/Workflow/"
> xmlns:smf="http://www.myco.com/xml/sa/4.0/smf">
> <soapenv:Header/>
> <soapenv:Body>
> <wor:ExecuteWorkflow>
> <wor:userCredentials>
> <smf:userId>03d27fc0-5ede-4cb8-89d7-6bf7510e16c6</smf:userId>
> <smf:applicationName>NA</smf:applicationName>
> </wor:userCredentials>
> <wor:workItem version="54">
> <smf:state>BECE5689-A575-4531-86B6-15176D827C08</smf:state>
> </wor:workItem>
> </wor:ExecuteWorkflow>
> </soapenv:Body>
> </soapenv:Envelope>
> Will cause the error to occur on trunk head, but the error won't occur if you revert changeset [765432] I do believe its to dow with the dynamic addressing breaking the partnerlink stuff, but I'm not clever enough to pin it down :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.