Theres a better way - put all your 'internal' pipelines in one and mark it
as internal...
map:pipelines
map:pipeline internal-only=true
!-- Internal matches here... --
/map:pipeline
map:pipeline
!-- external matches here... --
/map:pipeline
/map:pipelines
-Original Message-
From: Michael Homeijer [mailto:[EMAIL PROTECTED]]
Sent: Monday, 20 August 2001 11:17 am
To: '[EMAIL PROTECTED]'
Subject: Content aggregation and serializers
To my understanding, pipelines without serializers could be used in an
aggregator without exposing url of the aggregate part to the
outside world.
In the nightly build from thursday, each pipeline (also the
ones used in an
aggregator) requires a serializer.
Should I define internal pipelines in another way or was I on
the right way?
TIA,
Michael Homeijer
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
===
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
