anonymous wrote : Change an object while it is sitting in the session. The change does not get replicated. | | (You are supposed to call setAttribute() again, but nobody ever does.) |
Ah ok - whereas SFSB state is always replicated by the container at the end of the invocation? As a job lot? I guess it can't tell which instance variables you might have changed, so it has to replicate them all? anonymous wrote : Anyway, there are other good reasons to use SFSBs - they just support waaay more functionality than a dumb JavaBean, and are just as easy to write. Perhaps, but I'd just like to make sure I've understood your reasoning on the http session topic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3945838#3945838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3945838 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
