on 5/15/01 1:48 PM, "Sky Torch" <[EMAIL PROTECTED]> wrote:
> 1. is context object per request, i.e. each request
> may have its own context object ? from
> TurbineVelocityService class, it seems like it.
Yes. One context object per request.
> 2. since context object is passed to multi screen classes,
> all variables for dynamic data are within same context
> name space. therefore, a developer needs a complete set
> of these variable when write a new screen class.
> otherwise, he may override existing ones. is it a
> correct statement ?
Only one Screen class is executed per run.
> 3. if i write 3 templates:
> /direction/driving/map.vm
> /direction/train/map.vm
> /direction/train/ny/map.vm
>
> my module path is: com.company.modules
>
> each one requires its own dynamic data. i wanna implement
> 3 screens. what name and directory should these screens
> be put ?
A better design is:
<http://jakarta.apache.org/turbine/pullmodel.html>
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
