Yes, but we are interested in Post parameters. I think we have some ideas based on some of the other forum posts.
J.D. -----Original Message----- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Thursday, November 12, 2009 10:12 AM To: users@wicket.apache.org Subject: Re: Calling IN TO Wicket from JSP why dont we support them? dont browsers send us urls with query parameters??? -igor On Thu, Nov 12, 2009 at 9:03 AM, Corbin, James <jcor...@iqnavigator.com> wrote: > It seems like Wicket would support URLs with request parameters coming from > outside the wicket framework. I've looked at the WicketFilter code and it is > stripping the URL of its request parameters. It seems like a reasonable > thing to support. We are supporting a legacy application and integrating new > wicket displays that we need to call into from our legacy JSP app. > > I'm sure we are not the only ones doing this...I think PayPal had a similar > issue and I believe it was resolved, just not sure how. > > J.D. > > -----Original Message----- > From: Frank Silbermann [mailto:frank.silberm...@fedex.com] > Sent: Thursday, November 12, 2009 9:56 AM > To: users@wicket.apache.org > Subject: RE: Calling IN TO Wicket from JSP > > > When working within Wicket, we need not concern ourselves with the raw > content of the HttpServletRequest object, as our models are automatically > updated with the contents. However, I do believe Wicket provides you with > the ability to read the HttpServletRequest object if you wish to do so. > > Suppose that instead of providing your data as request parameters you POST > your form to the Wicket page. Then I imagine that your form data would be > contained within the HttpServletRequest object -- and your wicket page could > query it and obtain that data manually. Further interactions with the user, > then, would be through Wicket's native mechanisms. > > Caution is that I've never done this -- I'm just speculating. > > Frank Silbermann, Memphis, Tennessee > > On Thu, Nov 12, 2009 at 8:34 AM, Corbin, James <jcor...@iqnavigator.com> > wrote: >> That is exactly the issue that is causing the problem and what I need >> clarification on how to do.... >> >> J.D. >> >> -----Original Message----- >> From: Frank Silbermann [mailto:frank.silberm...@fedex.com] >> Sent: Thursday, November 12, 2009 9:23 AM >> To: users@wicket.apache.org >> Subject: RE: Calling IN TO Wicket from JSP >> >> The question, I think, is how to deliver request-specific parameters >> along with the URL to the Wicket page. For example, if a form in a JSP >> page is to be processed by a Wicket page, how can the JSP's form data to >> be delivered to the Wicket page? >> >> Is that the question? >> >>> -----Original Message----- >>> From: Jeremy Thomerson [mailto:jer...@wickettraining.com] >>> Sent: Thursday, November 12, 2009 9:59 AM >>> To: users@wicket.apache.org >>> Subject: Re: Calling IN TO Wicket from JSP >>> >>> I guess a more concrete example from you would be helpful. You should >> be >>> able to mount a page to a bookmarkable URL and then it will be easy to >>> create a URL to go into Wicket. >> >> >>>> -----Original Message----- >>>> From: Corbin, James [mailto:jcor...@iqnavigator.com] >>>> Sent: Wednesday, November 11, 2009 4:51 PM >>>> To: users@wicket.apache.org >>>> Subject: Calling IN TO Wicket from JSP >>>> >>>> Is it possible to build a wicket URL in a JSP that gets forwarded to >> and >>>> handle by the Wicket filter mechanism? >>>> >>>> This seems like it should be simple but doesn't appear to work right >> in >>>> 1.4.1. >>>> >>>> We build up a wicketized URL that makes it into the WicketFilter, but >>>> that filter strips all the request parameters. >>>> >>>> Any suggestions on how to approach redirecting from JSP into Wicket >>>> would be greatly appreciated. >>>> >>>> J.D. Corbin | IQNavigator, Inc. | Technology 6465 Greenwood Village >>>> Blvd, Suite 800, Centennial, CO 80111 | Office 303.563.1503 | Mobile >>>> 303.912.0958 | www.iqnavigator.com | jcor...@iqnavigator.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
