As working on the integration of Microcks as a DevService for Quarkus, it appears that it's challenging to have access to the MicrocksContainer devservice instance. This instance was initialized during the augmentation phase and - for the moment - I don't find any way of injecting it into the CDI context for later consumption by the hot replacer service.
Description
As the Quarkus components have access to the URL where the container is running that way:
we could propose a fallback where a static method of MicrocksContainer is used with an extra argument that is actually this microcksContainerUrl which is the Http endpoint.
Reason/Context
As working on the integration of Microcks as a DevService for Quarkus, it appears that it's challenging to have access to the
MicrocksContainerdevservice instance. This instance was initialized during the augmentation phase and - for the moment - I don't find any way of injecting it into the CDI context for later consumption by the hot replacer service.Description
As the Quarkus components have access to the URL where the container is running that way:
we could propose a fallback where a static method of
MicrocksContaineris used with an extra argument that is actually thismicrocksContainerUrlwhich is the Http endpoint.Implementation ideas
No response