Jann Forrer schrieb:
[...]
With our sitemap "API", we can barely change anything without breaking
backwards compatibility. We haven't introduced a way to declare
pipelines as private, so virtually all core and module pipelines can be
called by custom code. The same applies to XSLTs, JX templates and the
like.
yes is understand that but at least for publications, which are based on
the default publication, upgrade should be as easy as possible.
Well, IIUC this would mean that the core/module pipelines which are
called from the default publication define our sitemap "API". I have to
admit that I don't consider this sufficient.
A convention to solve this issue could be to prefix all "private"
pipelines with something like "lenyaInternal" or "lenyaPrivate":
<map:match pattern="lenyaInternal/*/*/…">
…
</map:match>
This could for instance be used for resource type format pipelines.
And with the module concept in 2.0 custom code is better isolated from
"lenya code".
This also doesn't really help to preserve backwards compatibility. You
can still call all module pipelines in your custom sitemaps ...
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
