Petals Sample Client

Endpoint mismatch when interface/service are the same

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.5.1
  • Fix Version/s: 1.5.2, 1.8.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Deploy 2 endpoints with same interface / service.
    Let's say : IF1 / SVC1 / EP1 and IF1 / SVC1 / EP2 .

    Invoke EP1 with sample client : works fine.

    Undeploy EP1 (su), and do the same invocation again (on missing endpoint EP1).

    EP2 is invoked by Petals.

    Wondering wether it is a bug... or a (undocumented) functionality ??

    Not that deploying 2 different EPs with same IF/SVC is definitely not a good SOA practice, if they are really supposed different - but this is not the point.

    Show
    Deploy 2 endpoints with same interface / service. Let's say : IF1 / SVC1 / EP1 and IF1 / SVC1 / EP2 . Invoke EP1 with sample client : works fine. Undeploy EP1 (su), and do the same invocation again (on missing endpoint EP1). EP2 is invoked by Petals. Wondering wether it is a bug... or a (undocumented) functionality ?? Not that deploying 2 different EPs with same IF/SVC is definitely not a good SOA practice, if they are really supposed different - but this is not the point.
  • Environment:
    Linux / JDK 1.6

People

Dates

  • Created:
    Wed, 31 Aug 2011 - 16:26:35 +0200
    Updated:
    Mon, 12 Mar 2012 - 18:39:21 +0100
    Resolved:
    Mon, 12 Mar 2012 - 18:39:21 +0100
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.