Hi.
AFAIK a Wicket user session and a EJB Session are separated. Meaning that
the EJB container decides whether a new EJB instance needs to be created or
not. However even if multiple Wicket sessions get the same EJB instance the
EJB container will still ensure proper synchronisation and transact
Hi,
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
serializable.
Please rise an issue for this (also quickstart would be great), and I
will look into it.
Best
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
