-
Bug
-
Resolution: Done
-
Critical
-
20.0.1.Final
-
None
The problematic pattern:
BinaryRequirement requirement = ...; ServiceName.parse(requirement.resolve(container, cache));
should be:
ServiceName.parse(requirement.getName()).append(container, cache);
- is cloned by
-
JBEAP-19999 [GSS](7.3.z) Hibernate/JPA custom 2LC regions generate wrong service names when region names contain a dot.
- Closed
-
WFLY-13690 InfinispanRoutingProvider generates wrong service names when server name contain a dot.
- Closed
- relates to
-
WFCORE-4707 OperationContext.getCapabilityServiceName(String, String...) generates wrong ServiceName if capability is not registered and dynamic part contains a DOT
- Closed