Mike Haberman wrote:
>
> >
> > > 1. In order to get the template that starts the whole shebang,
> > > there is a line in the ClassicPipeLine that does this:
> > > String layoutTemplate = Resolver.getTemplate("layouts", target);
> > > where target is the screen target.
> > >
> > > Unfortunately, this relies on the fact that getTemplate will
> > > return "layouts" + Default.vm if target is not found under "layouts".
> > > But it won't work if target is found under "layouts" and it's
> > > not obvious.
> >
> > Huh?
>
> Let's say you have the screen "CreateAccount.vm"
> layoutTemplate = Resolver.getTemplate("layouts", target)
>
> will look for CreateAccount in the directory layouts. It doesn't exist
> so the default is to return moduleType + "Default.vm" so you get
> "layouts/Default.vm" which works. But why are you choosing the layout
> template based on the screen name?
>
> That's what isn't obvious. You're relying on the implementation of
> getTemplate.
This has been the way the default TemplateService has worked since it
was coded.
John McNally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
