-
Bug
-
Resolution: Fixed
-
Neutral
-
3.0.0
-
None
-
None
Since bumping to Java 11 the following tests fail:
info.magnolia.rest.client.integration.RestClientDisabledIntegrationTest#invokeWhenClientIsDisabled info.magnolia.rest.client.integration.RestClientDisabledIntegrationTest#disabledClientsAreNotRegistered info.magnolia.rest.client.integration.RestClientOpenApiIntegrationTest#restCallsArePresent info.magnolia.rest.client.integration.RestClientOpenApiIntegrationTest#validateRestDefinition info.magnolia.rest.client.integration.RestClientOpenApiIntegrationTest#validateRestCallDefinition info.magnolia.rest.client.integration.RestClientOpenApiIntegrationTest#getPetById info.magnolia.rest.client.integration.RestClientOpenApiIntegrationTest#addNewPet info.magnolia.rest.client.integration.RestClientOpenApiMissingOperationIdIntegrationTest#restCallsArePresent info.magnolia.rest.client.integration.RestClientOpenApiMissingOperationIdIntegrationTest#validateRestDefinition
Looks like the changes from MAGNOLIA-8044 broke RestClientRegistry with the register and and onRegister callbacks not being called anymore.
See also MGNLRESTCL-178.
Acceptance criteria
- is caused by
-
MAGNOLIA-8044 Invert dependency between Registry and Configuration Source
- Closed
- is related to
-
MGNLREST-434 Change rest endpoint in Resource app does not trigger event to re-instance a new endpoint (6.3)
- Selected
- relates to
-
MGNLRESTCL-178 Build on JDK 11 (rest-client)
- Closed