Petals Studio

End-point update in a WSDL is sometimes wrong

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.3.3
  • Fix Version/s: 1.4.0
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide
    • Get a WSDL with two ports: a binding for SOAP and one for SOAP 1.2.
    • Change the end-point name in the JBI page.
    • Complete the wizard.

    There are high chances that the wrong binding will be updated by the studio.
    The binding type should be stored in the JBI page, so that the update is more precise.

    See WsdlUtils#updateEndpointAndServiceNamesInWsdl.

    Here is a sample WSDL with two bindings.

    <wsdl:service name="n_deploy" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_11">
    <soap:address location="http://xxx/ws_deploy_wcfservice/n_deploy.svc"/>
    </wsdl:port>
    <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_12">
    <soap12:address location="http://xxx/ws_deploy_wcfservice/n_deploy.svc/soap12"/>
    </wsdl:port>
    </wsdl:service>

    Show
    • Get a WSDL with two ports: a binding for SOAP and one for SOAP 1.2.
    • Change the end-point name in the JBI page.
    • Complete the wizard.
    There are high chances that the wrong binding will be updated by the studio. The binding type should be stored in the JBI page, so that the update is more precise. See WsdlUtils#updateEndpointAndServiceNamesInWsdl. Here is a sample WSDL with two bindings.
    <wsdl:service name="n_deploy" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"> <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_11"> <soap:address location="http://xxx/ws_deploy_wcfservice/n_deploy.svc"/> </wsdl:port> <wsdl:port name="ws_deploy_12" binding="i0:ws_deploy_12"> <soap12:address location="http://xxx/ws_deploy_wcfservice/n_deploy.svc/soap12"/> </wsdl:port> </wsdl:service>
  • Environment:
    -

Activity

Vincent Zurczak made changes - Fri, 14 Jun 2013 - 17:16:12 +0200
Field Original Value New Value
Fix Version/s 1.4.0 [ 10323 ]
Priority Critical [ 2 ]
Vincent Zurczak made changes - Tue, 29 Oct 2013 - 10:56:13 +0100
Status New [ 10000 ] Open [ 10002 ]
Vincent Zurczak made changes - Tue, 29 Oct 2013 - 10:56:22 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Vincent Zurczak added a comment - Tue, 29 Oct 2013 - 14:25:06 +0100

Notice the given sample is invalid.
Within a same service, port names must be unique.

However, it is true the current implementation updates the first SOAP binding it founds.
And this can lead to ambiguous situations when a service has 2 SOAP bindings.

Show
Vincent Zurczak added a comment - Tue, 29 Oct 2013 - 14:25:06 +0100 Notice the given sample is invalid. Within a same service, port names must be unique. However, it is true the current implementation updates the first SOAP binding it founds. And this can lead to ambiguous situations when a service has 2 SOAP bindings.
Vincent Zurczak made changes - Tue, 29 Oct 2013 - 15:36:52 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Vincent Zurczak made changes - Tue, 29 Oct 2013 - 15:36:57 +0100
Status Resolved [ 10004 ] Closed [ 10005 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
196d 22h 16m
1
Vincent Zurczak
Tue, 29 Oct 2013 - 10:56:13 +0100
Open Open In Progress In Progress
9s
1
Vincent Zurczak
Tue, 29 Oct 2013 - 10:56:22 +0100
In Progress In Progress Resolved Resolved
4h 40m
1
Vincent Zurczak
Tue, 29 Oct 2013 - 15:36:52 +0100
Resolved Resolved Closed Closed
5s
1
Vincent Zurczak
Tue, 29 Oct 2013 - 15:36:57 +0100

People

Dates

  • Created:
    Mon, 15 Apr 2013 - 13:39:17 +0200
    Updated:
    Tue, 29 Oct 2013 - 15:36:57 +0100
    Resolved:
    Tue, 29 Oct 2013 - 15:36:52 +0100