Petals BC SOAP

A SOAP consume does not manage correctly a call by service-name and endpoint name

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.0.7
  • Fix Version/s: 4.0.8, 4.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    With one Petals ESB node on which the following SU are deployed:

    • a SU 'A' providing: Itf1/Svc1/EP1
    • a SU 'B' providing: Itf1/Svc1/EP2
    • a SU 'C' consyuming: Itf1/Svc1/EP1

    When invoking the service Itf1/Svc1 through SoapUI, the endpoint EP1 is correctly invoked.

    If you undeployed SU 'A', the next SOAP UI invokation will be redirected on the EP2, that is wrong: on error should occurs.

    Show
    With one Petals ESB node on which the following SU are deployed:
    • a SU 'A' providing: Itf1/Svc1/EP1
    • a SU 'B' providing: Itf1/Svc1/EP2
    • a SU 'C' consyuming: Itf1/Svc1/EP1
    When invoking the service Itf1/Svc1 through SoapUI, the endpoint EP1 is correctly invoked. If you undeployed SU 'A', the next SOAP UI invokation will be redirected on the EP2, that is wrong: on error should occurs.
  • Environment:
    -

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
noddoux added a comment - Tue, 13 Sep 2011 - 18:19:14 +0200

Already fixed on the version 4.1 of the SOAP component because a message exchange creation refactoring was done

Show
noddoux added a comment - Tue, 13 Sep 2011 - 18:19:14 +0200 Already fixed on the version 4.1 of the SOAP component because a message exchange creation refactoring was done
Hide
Permalink
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:29:27 +0200

To merge in trunk

Show
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:29:27 +0200 To merge in trunk
Hide
Permalink
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:29:20 +0200

Fixed in branch petal-entreprise-3.1.x

Show
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:29:20 +0200 Fixed in branch petal-entreprise-3.1.x
Hide
Permalink
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:28:59 +0200

As PETALSSAMPCLIENT-1, the problem is due to the usage of the API ComponentContext.getEndpoint(ServiceName, EndpointName) where the returned value is not checked. The returne value null should throw an error instead of to be set in the MessageExchange that will force the Petals router to find an endpoint satisfaying only interface name and service name.

Show
Christophe DENEUX added a comment - Mon, 12 Sep 2011 - 09:28:59 +0200 As PETALSSAMPCLIENT-1, the problem is due to the usage of the API ComponentContext.getEndpoint(ServiceName, EndpointName) where the returned value is not checked. The returne value null should throw an error instead of to be set in the MessageExchange that will force the Petals router to find an endpoint satisfaying only interface name and service name.

People

Dates

  • Created:
    Fri, 9 Sep 2011 - 17:41:06 +0200
    Updated:
    Thu, 16 Feb 2012 - 17:06:38 +0100
    Resolved:
    Tue, 13 Sep 2011 - 18:19:14 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.