Petals SE JSR181

API too limited (can't obtain ServiceEndpoint)

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.2
  • Fix Version/s: 1.3.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Impossible to call an external endpoint by EP name, using the current APIs.

    The JBI context gives access to a MessageSender (see below), then we can fill in the interface / service names.

    But the Exchange doesn't provide any setEndpoint(endpointName). Instead, there is a setEndpoint(ServiceEndpoint)... but no API is accessible to generate a ServiceEndpoint starting from an endpoint name.

    This requires access to some of the Component's methods (or to the Component itself).

    // Example
    Exchange e = jbiContext.getMessageSender().createExchange(mep);
    e.setInterfaceName(myInterfaceName);
    e.setService(myServiceName);

    // How to set endpoint given an enpoint name ?? No way

    Show
    Impossible to call an external endpoint by EP name, using the current APIs. The JBI context gives access to a MessageSender (see below), then we can fill in the interface / service names. But the Exchange doesn't provide any setEndpoint(endpointName). Instead, there is a setEndpoint(ServiceEndpoint)... but no API is accessible to generate a ServiceEndpoint starting from an endpoint name. This requires access to some of the Component's methods (or to the Component itself). // Example Exchange e = jbiContext.getMessageSender().createExchange(mep); e.setInterfaceName(myInterfaceName); e.setService(myServiceName); // How to set endpoint given an enpoint name ?? No way
  • Environment:
    Petals 4.

Activity

People

Dates

  • Created:
    Wed, 7 Mar 2012 - 11:05:33 +0100
    Updated:
    Tue, 10 Apr 2012 - 19:21:14 +0200
    Resolved:
    Tue, 10 Apr 2012 - 16:03:35 +0200