im +1 for this change.
this feature would have simplified my implementation of providing xhtml
output.
i choose to derive from TurbineVelocityService to change the implementation
TemplatePageAttributes class.
A property file change would have been less code and cleaner.
(should i really have to derive a service to this?)
russell
> Sean Legassick wrote:
>
> On Wed, Feb 21, 2001 at 03:11:26PM +0000, Sean Legassick wrote:
> > It would be useful if the PullService could replace the hardcoded
> > placement of tools into the Context in TurbineVelocityService. I suggest
> > that the service allows specification of the scope of the tools as
> > follows:
> >
> > toolbox.tool.link.1 = org.apache.turbine.util.template.TemplateLink
> > toolbox.tool.link.scope = request
> > toolbox.tool.page.2 =
> org.apache.turbine.util.template.TemplatePageAttributes
> > toolbox.tool.page.scope = request
> > toolbox.tool.ui.3 = org.apache.services.pull.util.UIManager
> > toolbox.tool.ui.scope = global
>
> Amended proposal after IRC chat with Jason:
>
> toolbox.request.link.1 = org.apache.turbine.util.template.TemplateLink
>
> toolbox.global.ui.1 = org.apache.services.pull.util.UIManager
>
> one line per tool, cleaner...
>
> Also I think one ApplicationTool interface, but add an (Object data)
> parameter to init - this is consistent with the Initable interface.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
