Weld works good if the ejb3 container does not passivate the sfsb
or the http session ends.
This results in heavy crashes in the session.
The user at the client browser then must re-open a new session.
Perhaps weld looses alls its injections or does not call
take the correct classloader at this moment?
(I think weld sits between richfaces/servlets and the ejb container.
Must not weld aktivate the passivated sfsb ??)
Does somewhere known a workarround for this problem?
Or does weld need a separate jndi lookup if a session bean is passivated?
I have ni found an answer in the cdi spec.
Is there somewhere familiar with that problematic?