ingo schuster wrote:
>
> At 20:43 01/15/01, John McNally wrote:
> >services.TurbineTemplateService.default.screen=BaseJspScreen
>
> I had this value set... If I read the code right, following happens:
> DefaultPage calls ScreenLoader.getInstance()
> ScreenLoader calls TurbineAssemblerBrokerService.getAssembler()
> TurbineAssemblerBrokerService calls JavaBaseFactory.getAssembler().
>
> I can't see where the default screen comes into play. Did you mean that
> this screen is chosen if _no_ screen is defined?
> I _did_ set a screen in rundata, however it's one that does only exist as a
> template and not as a class.
>
> On the other hand, I got my stuff working by providing an own page module,
> so this is more a question of interest. I'm just wondering if I do
> something wrong in using turbine.
For a template foo/bar/index.jsp
A Screen (java class) will be search for as follows
foo.bar.Index
foo.bar.Default
foo.Default
Default
BaseJspScreen
the search takes place relative to the module.packages property. If
Turbine does not locate an appropriate Screen class, I do not think
things will work at all, unless you are placing the code from the
various parent Screen classes into your Page module.
If the Screen class that is associated with a template does not contain
a getLayout(RunData) method, the ancestor method will likely be looking
at the TR.props for a default.layout property.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
