Petals ESB Container

Honour topology's registry implementation on container attachment

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.1
  • Fix Version/s: 5.0.2
  • Component/s: Registry, Topology/network
  • Security Level: Public
  • Description:
    Hide

    Currently, if attaching to a topology that has a different registry implementation than the container's current one, the attachment will fail.

    Since #39415, during container moves, the endpoints are properly removed from the shared area in a generic format so that they can be reinjected in a different implementation of the shared area.

    We can thus now honour the topology's registry implementation during attachment without problems.

    Attachment will still fail if the implementation can't be found in the classpath (and on container start, the default implementation used will still be the one declared via the SPI in the classpath).

    Show
    Currently, if attaching to a topology that has a different registry implementation than the container's current one, the attachment will fail. Since #39415, during container moves, the endpoints are properly removed from the shared area in a generic format so that they can be reinjected in a different implementation of the shared area. We can thus now honour the topology's registry implementation during attachment without problems. Attachment will still fail if the implementation can't be found in the classpath (and on container start, the default implementation used will still be the one declared via the SPI in the classpath).
  • Environment:
    -

Activity

People

Dates

  • Created:
    Fri, 10 Jun 2016 - 11:43:03 +0200
    Updated:
    Fri, 10 Jun 2016 - 17:42:54 +0200
    Resolved:
    Fri, 10 Jun 2016 - 17:42:54 +0200