: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent
(@Persist).
Unless you are testing on a multi-machine cluster, you shouldn't
see any
problems along these lines!
On 5/7/07, Joel Wiegman [EMAIL PROTECTED] wrote
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 12:17 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent
(@Persist
, 2007 9:45 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
What annotations are on the brand field of your Main class?
Something
has changes that field to be read-only, which is usually a sign
that a
value
;
}
}
}
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Saturday, May 05, 2007 9:45 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
What annotations are on the brand field of your Main class? Something
has changes
)
... 48 more
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 2:32 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
In your OptionModel, the label is the Brand description, and the value
is the Brand itself
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent (@Persist).
Unless you are testing on a multi-machine cluster, you shouldn't see any
problems along these lines!
On 5/7/07, Joel Wiegman [EMAIL PROTECTED] wrote:
Impressive! I
PROTECTED]
Sent: Monday, May 07, 2007 12:17 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent (@Persist).
Unless you are testing on a multi-machine cluster, you shouldn't see any
problems along these lines!
On 5/7
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 12:17 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent (@Persist).
Unless you are testing on a multi-machine
${brand.description}
/t:if
/t:form
/html
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 12:17 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field
, May 07, 2007 12:17 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
Odd that you lost your value; the field is itself persistent (@Persist).
Unless you are testing on a multi-machine cluster, you shouldn't see any
problems along these lines!
On 5/7/07, Joel
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
In your OptionModel, the label is the Brand description, and the value
is the Brand itself.
You then supply a ValueEncoder that converts between Brands and brand
ids (as strings, for the client side). If Brand is an entity
Not to be harsh, but I don't think I've ever written a select box with
constant values (Enum). Seems like even Male/Female drop downs need to
be data-driven now-a-days. :-
I've started to stub out a very simple real world example of a select
component in T5, but it doesn't appear to be as
In the simplest case, T5 thinks that the options in the drop down list are
all strings.
In your case, they are Brands. The Select component doesn't know how to
create a client-side representation of a Brand (it doesn't magically know to
use the id).
You must provide a ValueEncoder that can
description to
the Brand object.
Just curious what your thoughts are on that...
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 1:42 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
In the simplest case, T5 thinks
: SelectModel - a real world example
In the simplest case, T5 thinks that the options in the drop down list
are all strings.
In your case, they are Brands. The Select component doesn't know how to
create a client-side representation of a Brand (it doesn't magically
know to use the id).
You must
-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 2:32 PM
To: Tapestry users
Subject: Re: T5: SelectModel - a real world example
In your OptionModel, the label is the Brand description, and the value
is the Brand itself.
You then supply a ValueEncoder that converts
16 matches
Mail list logo
