On Jun 2, 2006, at 1:21 AM, Igor Vaynberg wrote:
> for your particular usecase i see a simple and elegant solution:
> the form where you enter the url - that can be a separate form that
> populates a model for another form that contains the rest of the
> fields...that way i think everything will work smoothly.
Nope, that won't work. The submit button of the second form wouldn't
submit the first form, and I need the URL as well.
i dont know your usecase exactly, but you already have the url from
the previous submission, it will be available in its model when the
second form submits - remember this is all in the session
Not in every case. It could well be that the user goes right on and
fills the whole form with no assistance from the system. In that
case, no URL. It's hard to predict what a user would do, and having
everything on a single form looks like the only way to keep things
under control. Anyhow, with your suggestion, the code looks good
enough so I'm fine: I do think, though, that partial forms are
somewhat an important use case today, and it would be nice to
streamline that kind of operation within Wicket. Oh well, FFT and for
possible patches. :-)
Ciao,
--
Gianugo Rabellino
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
