-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jersey contextConfig support #26
Comments
Do you have a snippet you can post? I don't follow what you mean by: Do you need a way to control creation of the |
Yes that helps. How can i unbind the DefaultJerseyOptions? The HK2JerseyBinder is binding and my own binder is used once the DefaultJerseyOptions has already been used.
|
My idea was to replace DefaultJerseyOptions with the JerseyOptionsWithContextInfo class but i just noticed that the DefaultJerseyOptions are responsible for handling the binders option. Do you have a suggestion on how to deal with this usecase? |
Got it! I'm now extending the HK2JerseyBinder and using the _hk2_binder_ config instead of _binders_.
|
Yes, that is what I was thinking. Two things to consider:
|
It would be great if it would be possible to add support for the contextConfig resource config setting. In my case the setting is a spring AnnotationConfigApplicationContext object. The object can't be passed on to the DefaultJerseyOptions via the vert.x config mechanism. Do you have an idea how to handle this setting? I added a static setter to the DefaultJerseyOptions class in order to test it.
The text was updated successfully, but these errors were encountered: