Cool :) Be sure to test thoroughly. The session is really composed of 2
elements -- the attributes and the metadata (things like lastAccessedTime, id,
etc). The metadata is still replicated at the end of the request, so you may
get odd behavior.
View the original post :
http://www.jboss.com
Thank you. This configuration seems to produce the behavior I was expecting.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949935#3949935
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949935
_
No, it doesn't replicate at the start of the request.
In releases prior to 4.0.4, calling session.getAttributeNames() would mark the
session as dirty, thus causing replication at the end of the request. That's
why your "dump" call causes replication. I believe I changed that in 4.0.4.
I figur
Thank you.
Does it also replicate at the start of a request ? If it replicates at both
the start and end of a request that would explain the behavior I've observed.
Thanks for your help.
Tom
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949889#3949889
Re
The session replicates at the end of the request, not as modifications are
made. There is currently no way to change this behavior.
If this is important to you, please raise a feature request in the JBoss
Application Server project on jira.jboss.com.
View the original post :
http://www.jboss.c
Sorry, had some extraneous code in the example. The block of code commeted
"Hack to make the session replicate" should not have been there (it did not
make the session replicate). Below is the correct code.
Thanks,
Tom
<%@ page import="org.apache.commons.logging.Log" %>
| <%@ page import
