If you only store your form in request scope, Struts will create a new form object when the user submits it. It would also mean it will create a new instance of your business bean. To avoid this, you might consider placing your bean in session scope. Either way, though, you'll still have conversion issues to tackle if your business bean contains non-String fields, such as Dates or other custom objects. For those, you should register add'l Converter objects (BeanUtils comes with one for Date objecs). Take a look a FormDef (https://formdef.dev.java.net). Right now it doesn't allow you to selectively expose certain attributes, but it does define form beans based on the fields you have in your business beans. It might give you other ideas on how to deal with this issue.
Hubert On 5/27/05, Nils Liebelt <[EMAIL PROTECTED]> wrote: > Hi all, > > could I speed up my development by placing "business" beans inside a form > bean using delegating methods to set it. I could init the "business" bean > with a none bean method and only expose certain attributes of course > validating the way i need it. I am interested if I place such a construction > inside the request scope and submit the corresponding form. Is my nested > business object then still available or does Struts create a new form with > the set parameter? > > > Regards, > > Nils > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
