Joe Germuska wrote:
I'm happy to see this general pattern extended to any config element. The cost is pretty low, and in fact, consistency would be nice -- users shouldn't have to worry about where they can use the "key" attribute in <set-property>. Probably we should add some interface to cleanly represent the nature of "HavingArbitraryProperties"... although a good name is eluding me at the moment.
hmmm for now, just add the get/set methods? as in action mapping? :)
While I haven't needed it yet, ForwardConfig was my next likely candidate for this extension. Off the top of my head I can't think of anything which "shouldn't" have it. I'm just curious what you were thinking about doing with it in the form config objects?
Joe
FormPropertyConfig - the properties can provided hints in the view as to how that form-property would be rendered - specifically, customTags which can render a series of form-property(ies) without having to write the view jsp or other.
Likewise FormBeanConfig.
my thinking here is, for a singly project, the "action to view" would be quite standard. thus a lot of code can be removed by using these hints and a customTag
ps: will log n upload a patch (hopefully) soon.
:)
riyaz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
