It would be nice to implement a DynaBean version that can self-populate
or self-initialize the properties.
Say, if it were possible to encode property type in the
property name as: "myProp{MyPropClass}"
then the DyanBean's getter/setter can auto add a corresponding dyna
property.
This will enable any sub properties of MyPropClass to be invoked properly.
That is all possible, only if we extend the property specification to
include {type} part.
Do you feel this is a reasonable thing to do, or are there any pitfalls here
?
I am more interested in doing this with (Craig's soon to come)
DynaActionForm.
My end goal is to have one generic form bean (that will work for all
actions).
For such a generic form bean to handle multi-level properties
such as "myProp{MyPropClass}.subProp", it has to infer and initialize the
first property, so that the setter on the subProp can be invoked.
I am interested in knowing your thoughts and opinions on this.
If it does work out and I happen to implement it, I will provide a patch.
Thank you all for the great work !
Anil
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
