-
Notifications
You must be signed in to change notification settings - Fork 551
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
CDI Support for the Jersey/JAX-RS container? #20
Comments
Hi Niko, Thanks for the compliments and feedback. I will look into this. To help us narrow down the scope for a first release, is there something specific you are looking for? Could you give us some mock code of how you would like your tests to work like? S |
Hi @sapessi, Meanwhile, I started to implement the However, the unit-tests work fine, even with CDI. N. |
I got my example now working with Weld as CDI implementation. Yet, I don't know why this occurs, but I keep investigating and will compare classpaths... |
Let me know how it goes. I'll pick this issue up after I've added support for the Play framework. |
With the help from @bbilger, who has a similar project as yours https://github.com/bbilger/jrestless we found the solution in proper configuration of I've updated my above mentioned project and it's working pretty good. |
ah, good to hear. I'll keep this open to see if there is something we can include in the project to make the process easier. If not, I'll at least update the wiki to document this. |
In the 1.0 release of the library, we updated Jersey to 2.6. The latest version of Jersey can support multiple CDI methods. Resolving this. |
Ok guys, this is really awesome!
Thanks for doing this.
I've got the Spring integration up and running in minutes. It really works like a charme with all the Spring functionality included like autowiring etc.
The Jersey/JAX-RS integration also works quite good, but I would love to see some CDI support here as well. Is this somehow possible to provide a simple/small/lightweight CDI integration with Weld, Guice or something similar?
thx + regards,
Niko
The text was updated successfully, but these errors were encountered: