But, the main objective of shading is to let users embed their own Quartz
if I understood without interfering with TomEE internals.
So if they embed it, where is the issue? They gonna be able to
extend/implement whatever they want to.
JLouis
2013/12/3 Romain Manni-Bucau rmannibu...@gmail.com
But no more the tomee one without copying code. (once again not blocking)
Le 4 déc. 2013 09:35, Jean-Louis MONTEIRO jeano...@gmail.com a écrit :
But, the main objective of shading is to let users embed their own Quartz
if I understood without interfering with TomEE internals.
So if they embed
Thanks for your feedback Romain! Indeed this is not an easy thing to test.
The build is broken now; and it looks like this is the reason.
I will rollback the changes while I'm unable to create an unit test for it.
[]s,
Thiago.
On Wed, Dec 4, 2013 at 2:38 AM, Romain Manni-Bucau
Thanks!
I added a ApplicationConfig as suggested, and evth works properly now.
some further info here:
https://jersey.java.net/documentation/latest/deployment.html
--
View this message in context:
Trying the shaded approach would certainly be interesting.
There's a lot of merit to it if we can work through the obvious issues and test
the heck out of it.
-David
On Dec 3, 2013, at 12:57 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Ps: forgot another solutuon: shade quartz in
