You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that gRPC MP and SE client share configuration, which means that they both ultimately use Helidon SE Config, and depend on object-mapping to read complex config structure into a POJO that describes gRPC channel.
However, because we start everything up from MP world, we are loading MpConfig and converting it to Config. In the process, mapper services get disabled and this conversion doesn’t work any longer. However, if we comment out the line below within MpConfig.toHelidonConfig() that disables them, everything works fine:
The intention of the change was to get the same configuration as we have in MP. But that can never be the case.
So I think we can enable mappers and filters (to allow use of advanced Helidon SE features if developers want to)
The text was updated successfully, but these errors were encountered:
Environment Details
Problem Description
The issue is that gRPC MP and SE client share configuration, which means that they both ultimately use Helidon SE Config, and depend on object-mapping to read complex config structure into a POJO that describes gRPC channel.
However, because we start everything up from MP world, we are loading MpConfig and converting it to Config. In the process, mapper services get disabled and this conversion doesn’t work any longer. However, if we comment out the line below within MpConfig.toHelidonConfig() that disables them, everything works fine:
Response from @tomas-langer:
The text was updated successfully, but these errors were encountered: