Glen Ezkovich wrote:
> You seem to be assuming this is a global configuration
> issue. If I were to make this configurable I would do it on
> template by template basis, since it seems that in the
> general case this would not be necessary but in a special
> case it might be expedient. Once you turn it on globally, say
> hello to Barbara Eden, the genie is out of the bottle.
> Now if you could turn it on by pipeline in the sitemap, you'd
> be golden. From a user perspective I think it makes more
> sense to turn it on in the template as a processing instruction.
NB if the feature was enabled or disabled using an optional attribute on
the root element, it could still be controlled centrally through the
sitemap. To prevent template authors from enabling this feature, it
would be enough to transform their templates before execution to disable
the feature.
<map:match pattern="*.jx">
<map:generate src="{1}.jx"/>
<map:transform src="xsl/disable-java.xsl"/>
<map:serialize type="xml"/>
</map:match>
So you could lock this feature (or any feature) away from your template
authors. NB this is just another application of the general pattern of
"dynamic templates", something that was discussed at some length about a
month ago(?).
Cheers
Con
