On Tue, 14 Jun 2011 13:26:24 -0300, Muhammad Mohsen <m.gelb...@gmail.com>
wrote:
My original issue is that I need The bean editor to display an object of
type "TclRequest". This object contains simple properties (String,
boolean..etc.) and other POJOs. I need the BeanEditorForm to display
these POJOs exactly as it would with normal objects, meaning that when
it hit an object of type POP3TestData (Containing properties
String:gateway,
String:username..etc) in TclRequest, it would display edit fields
(TextField, Checkbox..etc) for "TclRequest"'s simple properties AND also
similar fields for POP3 request, in our case (2 TextField(s) for
"gateway" and "username".
A demonstration:
class POP3TestData{
String gateway;
String username;
}
class TclRequest{
String title:
POP3TestData pop3TestData;
}
So that when I use a BeanEditor to create a TclRequest, I would see 3
TextField(s), 1 for TclRequest.title and 2 for POP3TestData.gateway and
POP3TestData.username.
You can use a single edit block por POP3TestData and declare all the
fields yourself (gateway, username, title), just like you'd do directly in
a page, but receiving the object through PropertyEditContext.
So am I using the right feature here ? Which is to specify a datatype
POP3TestData and make a block in a page to edit an instance of this
object ?
I guess so.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
