Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-325

Dynamically assigning partnerLink EPR fails

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.3.0.Final
    • 2.2.0.CR1
    • Integration
    • None
    • Hide

      Create a BPEL workflow that assigns a static EPR from a literal (example above in description).

      Show
      Create a BPEL workflow that assigns a static EPR from a literal (example above in description).

    Description

      The dyamic EPR assignment operations from the ODE User Guide do not work. Specifically the cases for a Simple URL and a wrapped soap:address fail. This same operation performs correctly in ODE 1.3.4 in Tomcat 6.0

      These are the relevant portions of my BPEL spec:
      <bpel:partnerLinks>
      <bpel:partnerLink name="SafariFusionOssLink"
      partnerLinkType="sfWsdl:FusionOssLinkType"
      partnerRole="fusionOssService"
      initializePartnerRole="yes"/>
      </bpel:partnerLinks>

      <bpel:assign name="createFusionCreateRqst">
      <bpel:copy>
      <bpel:from>
      <bpel:literal>http://172.16.150.174:8080/safariap/OSS/FusionOss</bpel:literal>
      </bpel:from>
      <bpel:to partnerLink="SafariFusionOssLink"/>
      </bpel:copy>
      </bpel:assign>

      <bpel:invoke name="sendFusionCreateRqst"
      partnerLink="SafariFusionOssLink"
      portType="sfWsdl:FusionOssPort"
      operation="create"
      inputVariable="sndCreateRqst"
      outputVariable="sndEditResp" />

      From the WSDL:
      <plnk:partnerLinkType name="FusionOssLinkType">
      <plnk:role name="fusionOssService" portType="tns:FusionOssPort"/>
      </plnk:partnerLinkType>

      <wsdl:service name="FusionOss">
      <wsdl:port name="FusionOssSoap" binding="tns:FusionOssBinding">
      <soap:address location="http://localhost:8080/safariap/OSS/FusionOss"/> <!-- Note the different address -->
      </wsdl:port>
      </wsdl:service>

      When the invoke operation is performed the following exceptions are reported:
      18:26:32,954 ERROR [DispatchImpl] Cannot dispatch message
      java.io.IOException: Could not transmit message
      at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:229)

      ...

      Caused by: java.io.IOException: Could not transmit message
      at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:229)

      ...

      Caused by: org.jboss.ws.WSException: Invalid HTTP server response [404] - Not Found
      at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)

      Attachments

        Issue Links

          Activity

            People

              gary@brownuk.com Gary Brown
              wdarby William Darby (Inactive)
              Archiver:
              rhn-support-adandapa Aitik Dandapat

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty