To transfer from an action to a screen you can also use the RunData
data.getTemplateInfo() set/getTemp methods. This is also inderectly
available then in the template via the $data variable.
If it should be available directly in the template context you
should place it directly there. Note that the "pull model" beeing
discussed in this list is also presenting ways of pre-populating
the context (with buisiness objects).
:) Christoph
ingo schuster wrote:
>
> Hi,
>
> I wonder how in turbine data is supposed to be passed from an action to a
> template.
> The scenario: An action performs some processing (executing a query,
> whatever) and the results are to be displayed by a template (screen). The
> action results need to be made available to the template. How?
> I've seen that rundata holds a FormMessages field - am I supposed to use
> this? It seems to be rather unhandy for simple screens. Is there a way to
> store name/value pairs somewhere (in rundata)? The session is not really a
> good place for storing data with request-scope.
>
> ingo.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
