i guess it could be public, it isnt public because most of the time
you alter a variable inside session and then call dirty on the session
itself
But if you know your object is hold on to by the session and you are in that
object
itself, changing it then yes you also have to call dirty so i guess for this
kind
we just make it public.
johan
On 6/29/07, Maurice Marrink <[EMAIL PROTECTED]> wrote:
Hi,
I am in the process of making wasp and swarm play nicer within a
clustered environment.
Johan suggested calling dirty() whenever i make a change in the
session (which is where i store everything indirectly). But because i
have login method on my authorization strategy (which should call
dirty after a login) and Session.dirty() is protected i can not call
dirty unless i expose it in my WaspSession. Before i do that however i
thought i check here if there was a special reason not to make dirty()
public. I could not come up with one especially since bind is also
public which kind of has the same (side)effect.
So my question, what is the reason dirty() is not public and if there
is no reason could you make it public.
Thanks,
Maurice
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
