Thanks. I used your first email to give me context for a search in
the mailing list archives and eventually found the solution you
proposed. I'll let Kent Tong know he should mention it in his book,
too. I own TIA, but tend to go to Kent's book after one too many
false starts based on advice from TIA which is no longer valid in
Tap4, so I overlooked the solution in TIA. Hopefully, we'll get a
Tap4 version of the book some day soon.
--sam
On 3/6/06, Nick Westgate <[EMAIL PROTECTED]> wrote:
> Hi Sam.
>
> If you are using an externally posted form, you can use the
> names of the inputs:
>
> public void activateExternalPage(Object[] parameters,
> IRequestCycle cycle)
> {
> String userName =
> cycle.getRequestContext().getParameter("userName");
> setUserName(userName);
> }
>
> This example is from Howard's "Tapestry In Action".
>
> Cheers,
> Nick.
>
>
> Sam Gendler wrote:
> > I started out thinking that was the solution, but eventually wrote it
> > off because I couldn't figure out how to sort out which parameter to
> > assign to which property from the array of parameters passed in as
> > Object[]. I decided it must only be for use when creating an
> > ExternalCallback, since you can designate the order ot the parameters
> > in that case. I can't imagine that it just puts the parameters in the
> > order in which they are received, since http allows query string
> > parameters to be in any order. Am I missing something or will I have
> > to ensure that every browser sends the query string in the same order?
> > That strikes me as fragile.
> >
> > --sam
> >
> >
> > On 3/6/06, Nick Westgate <[EMAIL PROTECTED]> wrote:
> >
> >>Hi Sam.
> >>
> >>Check out IExternalPage:
> >>http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/IExternalPage.html
> >>
> >>Cheers,
> >>Nick.
> >>
> >>
> >>Sam Gendler wrote:
> >>
> >>>I have data in another application which isn't built on Tapestry. I
> >>>need to put a form on a page which isn't delivered by Tapestry, and
> >>>have it submit into my tapestry app. Is this even possible with the
> >>>rewind mechanism that Tapestry uses? I sure hope so, because my spec
> >>>also requires a login and password box in the header of every page in
> >>>the static website, and I need that form to submit to the Tapestry app
> >>>as well.
> >>>
> >>>In the first instance, it would be sufficient if I could just pass
> >>>parameters to Tapestry and then have tapestry serve up a form with the
> >>>supplied values already populating the form, requiring the user to
> >>>push a submit button to submit the form. In some instances, that is
> >>>actually the preferred mode.
> >>>
> >>>Any hints?
> >>>
> >>>--sam
> >>>
> >>>---------------------------------------------------------------------
> >>>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]
