Feature: Add config parameter for ProviderGatewayController context registration

[bcronin90]

WHAT

Adds an optional setting to specify a jetty context into which to register the ProviderGatewayController.

WHY

365

FURTHER NOTES

I don't know whether this is actually the correct approach.

Closes #365

[wolf4ood]

I would do mostly like the upstream management configuration does

https://github.com/eclipse-edc/Connector/blob/main/extensions/common/api/management-api-configuration/src/main/java/org/eclipse/edc/connector/api/management/configuration/ManagementApiConfigurationExtension.java

The important bit is .useDefaultContext(true) on WebServiceSettings.Builder which make it register to the default context if the context config key is not found, and it will make it backward compatible if no configuration is provided.

Let me know if this helps

[bcronin90]

I would do mostly like the upstream management configuration does

https://github.com/eclipse-edc/Connector/blob/main/extensions/common/api/management-api-configuration/src/main/java/org/eclipse/edc/connector/api/management/configuration/ManagementApiConfigurationExtension.java

The important bit is .useDefaultContext(true) on WebServiceSettings.Builder which make it register to the default context if the context config key is not found, and it will make it backward compatible if no configuration is provided.

Let me know if this helps

The problem there is that iirc we don't really have defaults for port and path. We just check whether they're provided and if they are not, we just like let the WebService handle things.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[paullatzelsperger]

removed my review, since @wolf4ood already commented.

[wolf4ood]

Thanks @bcronin90