> Apparently the form urlFor(IFormSubmitListener.INTERFACE) is > indifferent to the form id. How does it know which form is submitted > if there are two forms on the same page?
Ah.. probably the urlFor does some processing.. I wonder if I can transfer this 'capability' onto a component that is not the form itself. ** Martin > >> >> >> >> On Thu, Feb 19, 2009 at 5:05 PM, Martin Makundi < >> [email protected]> wrote: >> >>> I can actually 'bypass' the form very easily by setting >>> setRenderBodyOnly(true) and overriding the onComponentTagBody with >>> renderComponentTagBody(markupStream, openTag); >>> >>> My concern is on the processing side. >>> >>> How can I trigger/attach a suitable >>> requestListener/IFormSubmittingComponent? Preferably re-using some >>> existing component... >>> >>> <go method="post" href="???"> >>> <postfield name="IFormSubmittingComponent" value="XXX" /> >>> <postfield name="userId" value="$(userId)" /> >>> <postfield name="password" value="$(password)" /> >>> </go> >>> >>> >>> ** >>> Martin >>> >>> >>> 2009/2/19 Jeremy Thomerson <[email protected]>: >>> > I've never tried it, but I would suspect that I would start by creating >>> > something like: >>> > >>> > public class WapForm extends Form { >>> > protected void onComponentTag(final ComponentTag tag) { >>> > // copy the code from Form.onComponentTag to here and change the >>> > "action" and tag, etc... >>> > } >>> > } >>> > >>> > Form could also be changed to get the kind of tag and the attribute name >>> > ("action" / "href") from a method that could be overridden, but that >>> would >>> > require a change to core - this method you can do yourself quickly. >>> > >>> > >>> > -- >>> > Jeremy Thomerson >>> > http://www.wickettraining.com >>> > >>> > >>> > On Thu, Feb 19, 2009 at 3:35 PM, Martin Makundi < >>> > [email protected]> wrote: >>> > >>> >> > it's totally possible. did it at a company last year (but that's >>> >> > proprietary, of course). >>> >> >>> >> Cool. Can you give a hint if you could re-use Form components in Wml? >>> >> >>> >> <go method="post" href="???"> >>> >> <postfield name="userId" value="$(userId)" /> >>> >> <postfield name="password" value="$(password)" /> >>> >> </go> >>> >> >>> >> What is the best way to bind href and the postfields with a wicket >>> >> form? Or should I build a custom 'wap-form' which supports similar >>> >> validation? >>> >> >>> >> ** >>> >> Martin >>> >> >>> >> > >>> >> > Martin Makundi wrote: >>> >> >> >>> >> >> Hi! >>> >> >> >>> >> >> There has been some discussion in the past about using Wicket for >>> >> >> rendering WML pages: >>> >> >> http://cwiki.apache.org/WICKET/mobile-devices.html >>> >> >> >>> >> >> Is there any such wml+wicket boilerplate/quickstart code available >>> out >>> >> >> there or would someone like to post their experiences? >>> >> >> >>> >> >> ** >>> >> >> Martin >>> >> >> >>> >> >> --------------------------------------------------------------------- >>> >> >> To unsubscribe, e-mail: [email protected] >>> >> >> For additional commands, e-mail: [email protected] >>> >> >> >>> >> >> >>> >> >> >>> >> > >>> >> > -- >>> >> > View this message in context: >>> >> >>> http://www.nabble.com/WML-%2B-Wicket-experiences--tp22076991p22081338.html >>> >> > Sent from the Wicket - User mailing list archive at Nabble.com. >>> >> > >>> >> > >>> >> > --------------------------------------------------------------------- >>> >> > To unsubscribe, e-mail: [email protected] >>> >> > For additional commands, e-mail: [email protected] >>> >> > >>> >> > >>> >> >>> >> --------------------------------------------------------------------- >>> >> To unsubscribe, e-mail: [email protected] >>> >> For additional commands, e-mail: [email protected] >>> >> >>> >> >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
