Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.1
-
Fix Version/s: 5.0.2
-
Component/s: Registry, Topology/network
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
Currently, if attaching to a topology that has a different registry implementation than the container's current one, the attachment will fail.
Since r39415, 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). |
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). |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.2 [ 10661 ] | |
| Resolution | Fixed [ 1 ] |