Hi! In my experience this can be accomplished using stateless form. We have a login form on another site and it sends the parameters to a stateless wicket form.
** Martin 2009/11/12 Corbin, James <[email protected]>: > Thanks for the response, we are looking into doing something very > similar to this. > > -----Original Message----- > From: T Ames [mailto:[email protected]] > Sent: Thursday, November 12, 2009 10:09 AM > To: [email protected] > Subject: Re: Calling IN TO Wicket from JSP > > We are actually doing this with the POST as suggested below. Our > intranet > portal is in JSP, and passes info from the portal to individual Wicket > apps > in this manner. > > For me, these POST parameters appeared in the Request.getParameterMap() > > > > On Thu, Nov 12, 2009 at 11:55 AM, Frank Silbermann < > [email protected]> wrote: > >> >> 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 > <[email protected]> >> 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:[email protected]] >> > Sent: Thursday, November 12, 2009 9:23 AM >> > To: [email protected] >> > 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:[email protected]] >> >> Sent: Thursday, November 12, 2009 9:59 AM >> >> To: [email protected] >> >> 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:[email protected]] >> >>> Sent: Wednesday, November 11, 2009 4:51 PM >> >>> To: [email protected] >> >>> 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 | [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] >> > >> > >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
