>Hi All
>
>I have been using Turbine now for about two weeks, and I am still fairly
new to it.
>
>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;
You can follow 2 paths here:
1. If your validation applies more to a session (e.g. there need to be some
variables set for your application to execute properly) you can try and
implement a SessionValidator.
2. If you only need to see if the current screen should be displayed or not
(e.g. does a user have sufficient rights) you might want to take a look at
WebMacroSecureScreen.
>2. Retrieved page parameters
data.getParameters().getXXX()
> and stored relevant parameters into the session object, for later
> use by other pages.
data.getSession().setValue ("myValue",myObject)
OR
Add everything to the url of the following page with:
DynamicUrl url = new DynamicUrl();
url.lastUrl.addPathInfo (data.getParameters());
context.put (url);
>What is the recommended approach in Turbine to doing the same thing?
Depends on the situation
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
