You can also take a look at
https://github.com/wicketstuff/core/tree/master/wicketstuff-restannotations-parent
It provides an implementation of JAX-RS based on Wicket IResource
On Mon, Dec 3, 2018 at 9:29 AM Ernesto Reinaldo Barreiro
wrote:
> Ilia,
>
> Ok. Them "mounting" JERSEY as a wicket "res
Ilia,
Ok. Them "mounting" JERSEY as a wicket "resource" might be a solution?
On Mon, Dec 3, 2018 at 7:22 AM Илья Нарыжный wrote:
> Ernesto,
>
> WicketSessionFilter is cool workaround for most of cases, but in our case
> we need deeper integration. For example to have the same security model for
Ernesto,
WicketSessionFilter is cool workaround for most of cases, but in our case
we need deeper integration. For example to have the same security model for
wicket pages and rests.
Apparently, Jersey is not complex to integrate with. I already have more or
less working implementation of working
Hi Ilia,
If WicketSessionFilter not enough for your needs? It is a filter you can
put in front of JERSEY and you will have some wicket related things.
On Sun, Dec 2, 2018 at 6:50 PM Илья Нарыжный wrote:
> Hello,
>
> I know that story of wicket and different jax-rs containers is pretty long.
> C
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
