atbashee / atbash-config Goto Github PK

Instead of the class names which are shown at the moment.

When no @ModuleConfigName is specified, the class name is still kept as fall back.

With the usage of ServiceLoader?

Server -> MP application (outside of this repo) to retrieve configuration values from Rest Endpoint

Config source (within this repo, separate jar) to retrieve config values from server URL.

something like
pets: ["dog”,"cats”]

Other projects using atbash-config can benefit from a ConfigProviderResolver which configures a TestConfig which is a HashMap which can be configured for each test to have to required parameters.

We need to be able to define a parameter with different key names

for example

• loginPage -> used in the old Octopus; kept for backward compatibility.
• atbash.octopus.web.loginPage -> preferred name

So that we can have all our parameters in one file, but based on some System/environment variable select the correct set?

The following construct fails (with message that no converter is available for int)

    @Inject
    @ConfigProperty(name = "value2")
    private int value2;

But works fine with the real Geronimo Config

Contains also StringUtils, ClassUtils, ...

The implementation and the definition of the configuration file should be optional.

This avoids the MissingServiceLoaderConfigurationException when it is not defined.

Because in Atbash-config, we have defined the return type of the getOptionalValue() as T (and not Optional).

This results in UnknownMethod exception.

Although targetted to Java 7, a smooth upgrade should be possible.

The ResourceUtils.getInputStreamForPath works differently on Java SE as with Java EE when using the locator classpath:/resource.

When the resource is in the root, it is found in Java EE but not in Java SE. The construct classpath:resource needs to be used for that.

When trying to load a classpath resource and it is not found, also try without leading /.

In those cases where the logging is not required.

Like the OAuth2 clientId and clientSecret values for Octopus. But we need them for Google, LinkedIn, etc ...

Something similar then the property aware values of DeltaSpike https://deltaspike.apache.org/documentation/configuration.html#getPropertyAwarePropertyValue()

Several methods can be defined as helping reading optional values with defaults.