Hi Catalin, Good find on the 'formname:elementname' issue. I'm not sure whether isTransparentResolver() will solve the issue - you can try it and find out.
I ended up using a StatelessForm and redirect as I've document here: http://wiki.donohoedigital.com/wiki/Wiki.jsp?page=Bookmarkable%20Form%20Submission%20in%20Wicket I haven't looked into getting a single GET to work, however the solution would basically be putting the wicket stuff in hidden fields. In the meantime, the Stateless form and redirect is a decent interim solution. -Doug Catalin Marinas wrote: > > > Catalin Marinas wrote: >> >> I'm not sure that's the best way but I wanted to avoid calling >> onComponentTagBody in Form which generates the hidden fields. Ideally, I >> should use a WebMarkupContainer but, as you noticed, it adds the changes >> the elementname with formname:elementname. Somehow, the Form class >> manages to avoid this even though it inherits WebMarkupContainer but I >> couldn't figure out. Does anyone now how it does this? >> > > Looking through the code, it seems that the "formname:elementname" string > gets generated in FormComponent#getInputName(). This function checks > whether the parent is a Form and no longer adds the "formname:" string. > Since WebMarkupContainer is not a Form, it always does this. A solution > would be to override this function in any newly created FormComponent. > > Would overriding WebMarkupContainer#isTransparentResolver() to return true > have the same effect by attaching the children directly to the page? > > Thanks, > > Catalin > -- View this message in context: http://www.nabble.com/submit-form-to-bookmarkable-page-tp16912974p16993338.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]
