Absolutely, you want to use two BeanEditor components inside your own Form. Don't forget an Errors component and a Submit.
On Jan 8, 2008 3:39 PM, mammal <[EMAIL PROTECTED]> wrote: > > Hi, > > what is the best practice for doing the following registration form... > > let's assume we have a domain object User which contains several properties > and an Address object (which also contains several properties). I want to > create a registration form for such an object. So I create a page > RegisterUser that contains the User object > and beaneditform for the object. > > The Address bean is not included in the model though. I can try to insert > beaneditor for user.address manually into the template, but it's not > apparent how (except for appending it to some existing property editor using > <t:parameter name=""> which causes problems with markup) > > Another question is if I can insert an extra field like password2 (Retype > password) which I don't want to keep in User object. > > Also it would be nice if we can insert extra markup between property editors > at defined places. > > Maybe the best solution is not to use <t:beaneditform> but just plain > <t:form> containing several <t:beaneditor>s? > -- > View this message in context: > http://www.nabble.com/T5%3A-multiple-beaneditors-inside-a-beaneditform-tp14701908p14701908.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
