Yes. The former will let tapestry work its magic to ensure that
properties are properly cleared when the page is returned to the pool so
that other users don't access user-specific information.
The latter version won't.
Use the former.
Robert
Skriloff, Nicholas wrote:
When tapestry renders a page, is there any difference between
public abstract boolean getUserLoggedIn();
public abstract void setUserLoggedIn(boolean userLoggedIn);
AND
private boolean userLoggedIn;
public boolean getUserLoggedIn(){
return userLoggedIn;
}
public void setUserLoggedIn(boolean userLoggedIn){
this.userLoggedIn = userLoggedIn;
}
?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
