RE: RE: [JBoss-dev] can't use EJBs for HttpSessions.
c- we write a trivial CMP engine, in fact we don't write we plug in your distributed DSS thingy from the clustering UNDER the CMP store API and voila we have an entity semantic to find the stuff with your hashtable under the covers If this performs well, we will have proven one of the biggest points of EJB in JBoss. All it takes is putting that DSS in a CMP API wrapper. I've done it yesterday: - new PersistentStore backed with DSS (I've also commited a pure in-memory PersistentStore... just in case...) - new InstanceCache with distributed semantic i.e. if a bean modified on a node, all other nodes caches are cleared (of this particular bean) Now I will write the simple EJB with a dedicated stack (that uses these new layers) and possibly a helper JMX service (or simply some helper classes) that will simplify/wrap the usage of the bean. The helper service/class will also provide a mean to subscribe for cache update. Consequently, if Julian wants to keep a cache of HTTPSession, it can do it very easily witout loosing coherency. And this would really speed up things because as long as the cache is ok, there is no EJB=HTTPSession (i.e. byte[]=class) serialisation work to perform at all. Your dream is comming reality ;) Cheers, Sacha ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: RE: [JBoss-dev] can't use EJBs for HttpSessions.
Sacha, I'm still in the process of fixing Clustering to work with the new MBean invokers. I'll finish sometime tomorrow. It has taken me awhile to get things going after my laptop was stolen, but my wife is letting me work on JBoss tomorrow so I can finish up then. I'll just need somebody to test clustering on multiple machines since I only have access to one machine now. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sacha Labourey Sent: Sunday, December 30, 2001 4:56 AM To: marc fleury; [EMAIL PROTECTED] Subject: RE: RE: [JBoss-dev] can't use EJBs for HttpSessions. c- we write a trivial CMP engine, in fact we don't write we plug in your distributed DSS thingy from the clustering UNDER the CMP store API and voila we have an entity semantic to find the stuff with your hashtable under the covers If this performs well, we will have proven one of the biggest points of EJB in JBoss. All it takes is putting that DSS in a CMP API wrapper. I've done it yesterday: - new PersistentStore backed with DSS (I've also commited a pure in-memory PersistentStore... just in case...) - new InstanceCache with distributed semantic i.e. if a bean modified on a node, all other nodes caches are cleared (of this particular bean) Now I will write the simple EJB with a dedicated stack (that uses these new layers) and possibly a helper JMX service (or simply some helper classes) that will simplify/wrap the usage of the bean. The helper service/class will also provide a mean to subscribe for cache update. Consequently, if Julian wants to keep a cache of HTTPSession, it can do it very easily witout loosing coherency. And this would really speed up things because as long as the cache is ok, there is no EJB=HTTPSession (i.e. byte[]=class) serialisation work to perform at all. Your dream is comming reality ;) Cheers, Sacha ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] can't use EJBs for HttpSessions.
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 The user can not turn this optimization off since this is a container for the http sessions only. ok look i am tired of talking, marcf __ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66thread=6221 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] can't use EJBs for HttpSessions.
Hello Bill, I think that the goal was more to have something like this: HttpSession session = home.findByPrimaryKey(sessionId); byte[] state = session.getState (); // here Julian do whatever he wants with its state... // if he wants, he could convert its state in an Hashtable ... // and later session.setState (state); Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Bill Burke Envoyé : vendredi, 28 décembre 2001 06:38 À : [EMAIL PROTECTED] Objet : [JBoss-dev] can't use EJBs for HttpSessions. 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. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] can't use EJBs for HttpSessions.
Sure you can store the HttpSession state in an EJB(Entity or SFSB), but the HttpSession object cannot be an EJB. -Original Message- From: Sacha Labourey [mailto:[EMAIL PROTECTED]] Sent: Friday, December 28, 2001 4:36 AM To: Bill Burke; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] can't use EJBs for HttpSessions. Hello Bill, I think that the goal was more to have something like this: HttpSession session = home.findByPrimaryKey(sessionId); byte[] state = session.getState (); // here Julian do whatever he wants with its state... // if he wants, he could convert its state in an Hashtable ... // and later session.setState (state); Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Bill Burke Envoyé : vendredi, 28 décembre 2001 06:38 À : [EMAIL PROTECTED] Objet : [JBoss-dev] can't use EJBs for HttpSessions. 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. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] can't use EJBs for HttpSessions.
I guess what Im really saying is that you have to be careful if you're implementing the HttpSession in terms of EJBs. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Burke Sent: Friday, December 28, 2001 3:24 PM To: Sacha Labourey; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] can't use EJBs for HttpSessions. Sure you can store the HttpSession state in an EJB(Entity or SFSB), but the HttpSession object cannot be an EJB. -Original Message- From: Sacha Labourey [mailto:[EMAIL PROTECTED]] Sent: Friday, December 28, 2001 4:36 AM To: Bill Burke; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] can't use EJBs for HttpSessions. Hello Bill, I think that the goal was more to have something like this: HttpSession session = home.findByPrimaryKey(sessionId); byte[] state = session.getState (); // here Julian do whatever he wants with its state... // if he wants, he could convert its state in an Hashtable ... // and later session.setState (state); Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Bill Burke Envoyé : vendredi, 28 décembre 2001 06:38 À : [EMAIL PROTECTED] Objet : [JBoss-dev] can't use EJBs for HttpSessions. 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. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] can't use EJBs for HttpSessions.
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
