|
Congratulations ,
Tapestry will join Apache...
But I still hope someone can help me solving the
immature dumb question , which blocks me for one month...
I am developing a component , DateSelection , which uses
TextField for year ,
PropertySelection for month/day/hour/minute
.
I develop this component because this component can be used in
many situations,
such as user registration , order form processing
...etc.
But I found that TextField and PropertySelection must be
embedded in "Form",
which is initially pendent . That is , in DateSelection.html ,
there
should be a <form jwcid="selectionForm"> wrapping around
the year/month/day...
But the "DateSelection" will finally be embedded into other "Form",
such as user-registration form or
order-processing form.
Is such design correct ? I feel the "nested form"
queer ...
Or which is the proper design for this component
?
By the way , when developing DateSelection
component,
I have to write MonthPropertySelectionModel /
DayPropertySelectionModel /
HourPropertySelectionModel / and
MinutePropertySelectionModel ... which
implements IPropertySelectionModel .
Is this too overkill ? Is there any simpler way ?
|
