I'm not sure you can use an EntityBean or any type of EJB for that matter to
implement HttpSessions. Maybe I'm getting too religious here (meaning too
EJB spec oriented), but EJB semantics require that input parameters and
return parameters be serialized(copied). Sure, JBoss doesn't do this by
default, but maybe some users turn off this optimization to be EJB Spec
compliant. Why is this a problem? Consider that HttpSession is implemented
as an EntityBean.
You do:
HttpSession session = home.findByPrimaryKey(sessionId);
...
Then in user code:
Object attr = session.getAttribute("some attribute");
attr.setSomeValue("foobar");
Now, if HttpSession is implemented as an EntityBean, or SFSB, and
optimization was turned off, the attribute would not be changed within the
HttpSession.
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development