On Tue, 26 Sep 2000, Gopal Ramasammy-Cook wrote:
> I have been migrating one of my previous Web applications (just a small
> part) to Turbine. My old architecture had a "process" method in the Page
> class that effectively did:
> 1. Page validation;
If you meant that the pages should be validated against "Turbine login",
then create the pages by subclassing Screen or WebMacroSiteSecureScreen
(and don't change the default session validator, of course).
> 2. Retrieved page parameters and stored relevant parameters into the
> session object, for later use by other pages.
On your Screen's (the ones who serve the requests originating from your
HTML forms):
public ConcreteElement doBuild(RunData myRunData) throws Exception
{
ConcreteElement elem;
ParameterParser params = myRunData.getParameters();
User user = myRunData.getUserFromSession();
user.setTemp("mytempvalue", params.getString("myformsobjectname");
// somewhere on your other Screen's, you can use
// String s = user.getTemp("mytempvalue");
// put something on elem
return elem;
}
Oki
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
