Re: how to use dynamic partner link in BPEL ?

Probably your server ports were different from mine. Mine are default values. Error below sort of indicates that HTTP BC was not able to reach the service being called by BPEL's invoke.

-Kiran.

jsexton0 wrote:

Hello -

I downloaded the attached, loaded it up into my server (fresh install) and
ran the test case.  I got a 404.  The output is below.  Did I miss
something?  Thanks

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">BPCOR-6135:A fault was not handled in the
process scope; Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot; version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending errors
for the pending requests in the process scope before terminating the process
instance</faultstring>
      <faultactor xmlns="">sun-bpel-engine</faultactor>
      <detail xmlns="">
        <detailText>BPCOR-6135:A fault was not handled in the process scope;
Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot; version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending errors
for the pending requests in the process scope before terminating the process
instance
   Caused by: BPCOR-6131:An Error status was received while doing an invoke
(partnerLink=PartnerLink3,
portType={http://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType,
operation=PartnerWSDLOperation)
BPCOR-6129:Line Number is 59
BPCOR-6130:Activity Name is Invoke2
   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>



Kiran Bhumana-2 wrote:
  

Hello Mithun,

I looked at your project. What you can change is the address, not the 
service and port. We are working on improving HTTP BC so that you can 
change the service and port as well. But for now, take it that the 
HTTP-BC needs to know that the service and port that you are providing 
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at 
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is 
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I 
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so 
users can reuse these BPELs to construct the Dynamic endpoint structure. 
Let me know if that helps in any way.

Thanks,
Kiran B.

 

    

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)