Startup fails if @Provider constructor has @ConfigProperty

[David Hoffer]

I have a custom ContainerResponseFilter that Is marked as @Provider but gets config values from @ConfigProperty when created.  At startup I get NPE in ConstructorInjectorImpl line 55.  Why?

I have several other places where @ConfigProperty works fine in constructor. 

How to pass config values to ContainerResponseFilter?

-Dave

[Georgios Andrianakis]

Unfortunately this is a problem we have seen before in RESTEasy Classic (it works as expected in RESTEasy Reactive).

I would suggest working around the problem using

ConfigProvider.getConfig().getValue(...)

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/26a0fbd3-d6e0-407d-90b7-634cbf25d47en%40googlegroups.com.

[Guillaume Smet]

Could you create a GitHub issue with a reproducer attached?

Thanks!

--

[David Hoffer]

I did use ConfigProvider.getConfig() as a workaround as was suggested however now that class can't be unit tested.

Also just some feedback on the  ConfigProvider.getConfig().getValue (String propertyName, Class<T> propertyType) operation.

It's not very friendly to use as my response type is List<String>.  So I had to change to this:

ConfigProvider.getConfig().getValue("app.response-headers", String[].class);

But that array can be empty and if that happens it throws NoSuchElementException...but it does exist...just empty.

So I have to do this:

String[] responseHeaders = new String[0];
try {
responseHeaders = ConfigProvider.getConfig().getValue( "app.response-headers"  , String[].class);
} catch (Exception ignored) {
}

Lot of code just to read one property.  Is getOptionalValue() to help solve this?  Does it catch the exception?  Even if actually does not exist?  I can't think of a good reason to ever throw...just want whatever exists if any.  Having a default value is useful but I don't see that option.

Thanks,

-Dave

[George Gastaldi]

Use 

@Inject @ConfigProperty(name="yourprop")

Instance<List<String>> instance;

And call instance.get() inside your filter() method

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/d360d903-3398-4387-80ec-7a95a9491156n%40googlegroups.com.