|
A few
comments on the comments:
1. Not
really, to make it nice and portable, I use the generated forms as a base and
extend it with what else I need bubbled to the front end. Say a
java.sql.Date, I like to collect it as three seperate String, see if it a valid
date then set it, so my extended form has these three seperate fields and in
validation, if they all match up I set the actual java.sql.Date. Found
this works quite nice.
2.
Agreed, as you see above, I do manual merging, but I think to keep the
generation as generic and usefull to the most people, then extending the form
becomes a good solution.
3. I
absolutly agree that a setData would be great, and should be prety easy to add
in, the getData but change x=y to y=x.
I am using XDoclet CVS version for a
J2EE(jboss)/Struts project and you guys kick a$$.
Possible Solution in struts_form.j
public void
setData(<XDtEjbDataObj:dataObjectClass />
dataHolder)
{ <XDtStrutsForm:forAllFormFields> this.XDtMethod:getterMethod/>(dataolder.<XDtMethod:setterMethod/>()); </XDtStrutsForm:forAllFormFields> } Later,
Jake
T.
|
Title: Message
- [Xdoclet-user] Struts Form comments Michael Szlapa
- [Xdoclet-user] NullPointer in <packageSubstitution&... Michael Szlapa
- RE: [Xdoclet-user] NullPointer in <packageSubst... Ara Abrahamian
- Re: [Xdoclet-user] NullPointer in <packageS... Michael Szlapa
- RE: [Xdoclet-user] NullPointer in <pack... Ara Abrahamian
- Jake Thompson
