Thanks a lot for all that feedback. I think it gets me a step further.
Tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 8/30/06, Tom Bednarz <[EMAIL PROTECTED]> wrote:
What is the correct or preferred way to link business-objects with form
beans. Is this only possible by copying data from a business object to a
form bean or is there any 'smarter' way?
You might want to take a look at FormDef: https://formdef
Tom Bednarz wrote:
So I used
Don't specify value. Simply copy the properties from a subscriber
object (session scoped or otherwise) to a formbean (the one being used
to render the form values). There's a copyProperties method in
org.apache.commons.beanutils.BeanUtils:
http://tinyurl.c
Thanks a lot for all your input and help. It looks like I need some
basic concepts clarified. Here a very short background of the
application and what my intension is:
The object 'subscriber' is a special business object: it represents the
logged in user and contains a lot of information about
Tom Bednarz wrote:
David Durham wrote:
Tom Bednarz wrote:
I think the validator fires too early, but probably I am doing
something wrong. Maybe somebody can hp!
Basically, you need 2 actions, one to populate the form and one to
change the personal data.
Or at least two action mappings, if
On 8/30/06, Tom Bednarz <[EMAIL PROTECTED]> wrote:
The idea is, that I show a form that contains already data and the user
can edit it. When the form is submitted, the validator should check the
user input. Here is my validator configuration:
...
Now it seems, that the validator gets fired BEF
Why are you making these fields so complex? You have
Instead of the simple form:
?
Why do you need to specify all of that redundant information like value and
name when you have the property attribute? And why are you pulling values
from the session scope instead of the request data that
David Durham wrote:
Tom Bednarz wrote:
I think the validator fires too early, but probably I am doing
something wrong. Maybe somebody can hp!
Basically, you need 2 actions, one to populate the form and one to
change the personal data.
David,
This is EXACTLY what I like to AVOID! With th
Tom Bednarz wrote:
I think the validator fires too early, but probably I am doing something
wrong. Maybe somebody can hp!
Basically, you need 2 actions, one to populate the form and one to
change the personal data.
I have the following form bean defined in struts-config.xml:
type="o
9 matches
Mail list logo
