A page's activate event handler can work very much like a servlet: you can inject the Request object and read query parameter values from it and do what you like. Then the page will render, or you can return a value from the active event handler method to direct Tapestry to render something else. I've used this for cheap-and-easy JSON rest services, for example.
On Mon, Jul 26, 2010 at 1:03 PM, DavidWei <xinhua....@rrd.com> wrote: > > Hi, > > I am working on consolidating login processes of two web applications with > single sign-on. The Main app is not written in Tapestry, but the other is. > So when the user logs in the main app, there will be a link to the Tapestry > application by passing some login information through form post, which will > be used to decide what pages this user can view. > > What should I do to read the post information from external non-tapestry app > inside the tapestry app? > > Thanks in advance, > > David > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/Process-form-post-from-non-trapestry-site-tp5339551p5339551.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
