Илья Нарыжный
2018-12-02 17:50:00 UTC
Hello,
I know that story of wicket and different jax-rs containers is pretty long.
Currently we are using Jersey as a servlet under wicket filter, but we
don't like that in this case REST end-points have nothing about Wicket: no
wicket session available, no wicket request cycle listeners executed and
etc.
There is an idea to implement IRequestHandler which will handle as Jersey
Container. So it will be executed under wicket umbrella.
Questions:
1) What do you think about this?
2) Is there some existing implementation of what I'm talking about?
Please reply also even in a case if you interested in this library. It will
help me to understand: does it worst to make this integration as a separate
library or we can embed into our code within Orienteer.
Thanks,
Ilia
---------------------------------------------
Orienteer(http://orienteer.org) - open source Business Application Platform
I know that story of wicket and different jax-rs containers is pretty long.
Currently we are using Jersey as a servlet under wicket filter, but we
don't like that in this case REST end-points have nothing about Wicket: no
wicket session available, no wicket request cycle listeners executed and
etc.
There is an idea to implement IRequestHandler which will handle as Jersey
Container. So it will be executed under wicket umbrella.
Questions:
1) What do you think about this?
2) Is there some existing implementation of what I'm talking about?
Please reply also even in a case if you interested in this library. It will
help me to understand: does it worst to make this integration as a separate
library or we can embed into our code within Orienteer.
Thanks,
Ilia
---------------------------------------------
Orienteer(http://orienteer.org) - open source Business Application Platform