Hi Carlos,
thanks so much for your explanation. Your 1st reply was already helpful as I
was able to notice my mistake after you pointed it out :-). I apologize for
posting sample code with such an obvious mistake in it.
By the way, the page is working as it should now... Best regards,
Cristina
Carlos Pita-4 wrote:
>
> Sorry, I will try to be a bit less laconic this time :). You should be
> creating a blank Employee to set as the model object. It could be
> created from scratch upon each incoming request using a detachable
> model (for example, if Employee is not Serializable), or just be a
> simple Serializable field of your page or form class with a value
> other than null, of course. In the second case you can instantiate the
> Employee just once, during page creation, and it will be stored into
> the wicket session.
>
> Regards,
> Carlos
>
> On 9/10/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
>> > private Employee e;
>> [...]
>> > public LoginForm(final String id) {
>> > super(id);
>> > setModel(new CompoundPropertyModel(e));
>>
>> Notice that your model is null.
>>
>> Regards,
>> Carlos
>>
>> On 9/10/07, Cristina <[EMAIL PROTECTED]> wrote:
>> >
>> > Hello,
>> >
>> > I'm trying to set up a simple login page where the password is
>> retrieved
>> > from the DB if the username exists. [...]
>
--
View this message in context:
http://www.nabble.com/Setting-up-a-very-simple-login-page-tf4419382.html#a12625120
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
