Hi!

Again, I'm new, so hopefully I'm not posting in a bad way here. I've looked
through the forum but couldn't find the answer. Couldn't find the answers
from Tapestry in Action (I'm sure they are there if anyone can point me at a
page).

I have a simple page and form as below. The AuthenticationModel is a
LoadableDetatchableModel that queries the database for a username/password
based on a cookie id (I've cut all this code out for the example below).

My questions are perhaps super naive, but for some reason I am panicking
about serialized objects:

1) Exactly WHAT is getting serialized and where and when?

2) What are the main classes in the framework responsible for serialization
that I can look at (I have the source)? I guess I am after understanding the
flow of logic.

3) What happens if I make userIdField and passwordField scoped to the
constructor only? Is it common not to have them as member objects and why?
(I've not tried this yet, just wondered).

Many thanks for any help once again...

public class LoginPage extends AbstractWebPage
{
    public LoginPage()
    {
        // create a login form and add it to the page
        add( new LoginForm() );        
    }   
}

public class LoginForm extends Form
{
    private static final long serialVersionUID = 3975327499669581927L;

    private TextField userIdField;

    private PasswordTextField passwordField;

    public LoginForm()
    {
        super( "loginForm", new AuthenticationModel() );

        userIdField = new TextField( "username", new PropertyModel(
authenticationModel, "username" ) );

        passwordField = new PasswordTextField( "password", new
PropertyModel( authenticationModel, "password" ) );

 
        // add the components to the form
        add( userIdField );
        add( passwordField );
    }

    @Override
    protected void onSubmit()
    {
        // authenticate user
    }
}
-- 
View this message in context: 
http://www.nabble.com/How-does-serialization-work--tp20311180p20311180.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to