At first thought, please try your code out with wicketstuff
javaee-inject, but it will most likely behave just the same.
You cannot store your bean in session, because AFAIK they're not
Please rise an issue for this (also quickstart would be great), and I
will look into it.

Best Regards,
Peter Major

2010-03-18 10:07 keltezéssel, Christian Reiter írta:
> Hi!
> I've just started using the @EJB injection annotation from
> wicket-contrib-javaee.
> I use it to inject a Stateful Session Bean to keep track of my user
> session and do some
> stuff like authorization.
> I thought the @EJB annotation keeps track of my sessions and would
> inject a unique instance of
> the Stateful Session Bean for each of my Wicket session.
> But, it injects always the same Stateful Session Bean instance
> completely ignoring my Wicket sessions. In this case it is useless to
> keep track of my users.
> Am i doing anything wrong or is this the intended behaviour?
> Would it be better to get the Stateful Session Bean by a lookup call and
> then store it in the
> Wicket session?
> Thanks for your help!
> Best Regards,
> christian

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to