Petals ESB Container

ComponentContext.resolveEndpointReference(DocumentFragment) only relies on the local endpoints

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 5.0.0
  • Fix Version/s: None
  • Component/s: ComponentContext
  • Security Level: Public
  • Description:
    Hide

    Currently, the resolveEndpointReference method of the component context tries to resolve endpoints only by relying on the components installed on the local node.

    It should resolve them using the whole topology, maybe using the EndpointDirectory, but this is not trivial because resolving endpoint is something that can only be done dynamically by a component, you can't really store the resolved endpoint in a shared space and resolve it there...

    The idea of resolving endpoint reference is maybe not the best w.r.t. distribution...

    Maybe in the future we should rely on the distributed computing capabilities of the SharedArea implementation (hazelcast) to solve this problem...

    Show
    Currently, the resolveEndpointReference method of the component context tries to resolve endpoints only by relying on the components installed on the local node. It should resolve them using the whole topology, maybe using the EndpointDirectory, but this is not trivial because resolving endpoint is something that can only be done dynamically by a component, you can't really store the resolved endpoint in a shared space and resolve it there... The idea of resolving endpoint reference is maybe not the best w.r.t. distribution... Maybe in the future we should rely on the distributed computing capabilities of the SharedArea implementation (hazelcast) to solve this problem...
  • Environment:
    -

Issue Links

People

Dates

  • Created:
    Wed, 6 Jan 2016 - 11:17:34 +0100
    Updated:
    Mon, 25 Jan 2016 - 09:37:17 +0100