You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Christoph Henrici <ch...@dplanet.ch> on 2002/01/09 21:40:56 UTC
Understanding cocoon ......
I have been studying, testing and playing around with cocoon in the
last few days as a newcomer : i am greatly impressed with what ease with
cocoon "pipelines" arbrary data sources can be "chained" to a result
target: a very powerful paradigm (pipe) applied in a powerful context
(http) by using great technology (xml, xlst). In context of the
development of a web based application with requirements for a fairly
generic mechanism for the dynamic personlization of webpages in terms of
content and style the following questions below arised. Maybe they stem
from the fact, that i still missed a couple of aspect and points, maybe
the requirement or idea is just not thought through enough, anyway:
a. Is it possible to "compose" pipelines and having the composed
pipeline beeing processing bottom-up and the whole beeing rendered for
example as html: A compostion of tables within table, frames within
frame etc., where the content of the "elementary" pipelines are
dyanmic, taking for examples data from the databases. I am aware that
the aggregation <map:aggregate> mechansim provides a somewhat similiar
construction, only the composition could also be composed of aggregations.
b. Is it possible the change the sitemap or more specifically the
piplines configuration ( <map:pipelines>) dynamically.
If this can be achieved with cocoon 2 i would be very grateful for a
rough outline on how. If some additional development would be needed it
would be great to have some starting hints at where to start looking at.
Any other ideas or suggestions with regard to the requirement are also
greatly appreciated.
Christoph Henrici
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Understanding cocoon ......
Posted by Christoph Henrici <ch...@dplanet.ch>.
Stefano Mazzocchi wrote:
>Christoph Henrici wrote:
>
>> I have been studying, testing and playing around with cocoon in the
>>last few days as a newcomer : i am greatly impressed with what ease with
>>cocoon "pipelines" arbrary data sources can be "chained" to a result
>>target: a very powerful paradigm (pipe) applied in a powerful context
>>(http) by using great technology (xml, xlst).
>>
>
>Yep, I think you really hit the point. Some people believe that it's
>enough to add server side transformation capabilities (say, adding a
>XSLT post-processor as a servlet filter!) to come up with a publishing
>framework.
>
>But without a solid and well designed internal component architecture
>this is definately not true.
>
You definitely miss a framework with a high degree of reusability,
entensability and a high degree
of configurability achieved through the component architecture. It' s
like with all, you start with solving
specific problems and as your requirement space grows you evolve at
least the paradigm: good software has
to make well balanced decisions between meeting specific requirements
and generic solutions. I think cocoon 2
achieves this extremly well, especially now with the understanding of
your below elaborations.
>>In context of the
>>development of a web based application with requirements for a fairly
>>generic mechanism for the dynamic personlization of webpages in terms of
>>content and style the following questions below arised. Maybe they stem
>>from the fact, that i still missed a couple of aspect and points, maybe
>>the requirement or idea is just not thought through enough, anyway:
>>
>>a. Is it possible to "compose" pipelines and having the composed
>>pipeline beeing processing bottom-up and the whole beeing rendered for
>>example as html: A compostion of tables within table, frames within
>>frame etc., where the content of the "elementary" pipelines are
>>dyanmic, taking for examples data from the databases. I am aware that
>>the aggregation <map:aggregate> mechansim provides a somewhat similiar
>>construction, only the composition could also be composed of aggregations.
>>
>
>There are two 'flavors' of aggregation in Cocoon: generation-based and
>transformation-based.
>
>The first is done with the use of the <aggregate> semantic include in
>the sitemap. In fact, an aggregator is nothing but a special generator,
>but it was decided to place directly into the sitemap semantics since it
>is very useful.
>
>The problem with this approach is that the parts must be defined at
>sitemap-design time. While this normally covers 90% of the cases, in
>some other cases (my-netscape-like portal applications, for example) the
>aggregation is driven by environment information (say: user preferences)
>thus cannot be specified in the sitemap (unless everything is aggregated
>and then filtered out, but this is not performant at all, expecially for
>very complex portals).
>
>For this reason, another solution is present, which is based on
>server-side xinclude expansion performed at a transformation stage.
>
>In short: the pipeline contains some namespaces that indicate 'include'
>behavior and the transformer acts as an aggregator but on 'part'
>information which is previously generated, so might come from any
>source.
>
>it is easy to imagine a generator that gets the details about the user
>preferences out of a session bean (or ejb, database, file, whatever) and
>streams them on the pipe, letting the subsequent transformer performing
>the aggregation.
>
>of course, all this is cache-aware.
>
>>b. Is it possible the change the sitemap or more specifically the
>>piplines configuration ( <map:pipelines>) dynamically.
>>
>
>No and I will continue to veto it until somebody changes my mind.
>
>I think dynamic pipelines are *bad* and so far, nobody was able to come
>up with a meaningful example that *required* dynamic pipelines and
>couln't be done with better pipeline components.
>
Yes, i agree now, understanding very much more about the two approaches
to aggregation.
>>If this can be achieved with cocoon 2 i would be very grateful for a
>>rough outline on how.
>>
>
>Check the XIncludeTransformer and the CIncludeTransformer.
>
I'll do that ....combined with the generator based approach, maybe even
combined with a
aggregation / filter approach ......
>>If some additional development would be needed it
>>would be great to have some starting hints at where to start looking at.
>>Any other ideas or suggestions with regard to the requirement are also
>>greatly appreciated
>>
>Hope this helps.
>
Yep, definitely.
Christoph Henrici
Re: Understanding cocoon ......
Posted by Peter Royal <pr...@managingpartners.com>.
On Thursday 10 January 2002 08:15 am, Stefano Mazzocchi wrote:
> > b. Is it possible the change the sitemap or more specifically the
> > piplines configuration ( <map:pipelines>) dynamically.
>
> No and I will continue to veto it until somebody changes my mind.
>
> I think dynamic pipelines are *bad* and so far, nobody was able to come
> up with a meaningful example that *required* dynamic pipelines and
> couln't be done with better pipeline components.
As a former dynamic-pipeline advocate, I have seen the light :) Thus I'm just
offering support for your position. Its *much* easier to maintain a static
pipeline, it did require some rethinking of how to do things, but its all
better in the end.
-pete
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Understanding cocoon ......
Posted by Robert Koberg <ro...@koberg.com>.
Howdy,
> ----- Original Message -----
> From: "Stefano Mazzocchi" <st...@apache.org>
> Robert Koberg wrote:
> >
> > Hello,
> >
> > > ----- Original Message -----
> > > From: "Stefano Mazzocchi" <st...@apache.org>
> > > Christoph Henrici wrote:
> > > >
> > > > I have been studying, testing and playing around with cocoon in
the
> > > > last few days as a newcomer : i am greatly impressed with what ease
with
> > > > cocoon "pipelines" arbrary data sources can be "chained" to a result
> > > > target: a very powerful paradigm (pipe) applied in a powerful
context
> > > > (http) by using great technology (xml, xlst).
> > >
> > > Yep, I think you really hit the point. Some people believe that it's
> > > enough to add server side transformation capabilities (say, adding a
> > > XSLT post-processor as a servlet filter!) to come up with a publishing
> > > framework.
> >
> > I guess I am one of those :) But I guess you are talking about much
broader
> > publishing needs. It is all relative.
>
> Oh, yes. I was not referring to ad-hoc solutions but to who wants to
> take a publishing system (say Turbine), add an XML transformation
> language on top (say DVSL*) and voila': who needs Cocoon?
>
> (*) http://jakarta.apache.org/velocity/dvsl/index.html
>
> > I have not used cocoon2 yet. I had very bad experiences adopting cocoon1
> > (right when it came out -- MacMillan's idiotsguides.com - god, I wish I
> > could take that one back :( for many things besides cocoon's PIs - my
first
> > "real" web-site...). When I understand what I needed (too late) I
realized
> > that cocoon was the furthest thing. I am hoping to gather this info
about
> > cocoon2 from you guys (and maybe throw my 2cents in every now and then
:).
> > It sounds like you have a fantastic product. I would have installed it
to
> > play around with but all the other things you need... Then again, all
the
> > buzz makes it very interesting.
>
> I've talked with many people that were scared away by Cocoon1. No excuse
> there: it was a first try and a pretty home-made one. But considering
> that the XML model is not yet finished, the XML spec is 4 years old and
> Cocoon is 3 years old, I think that we did have a good excuse to try
> things out.
I jumped on board and really loved the ideas. It got me thinking in this
direction so I am very appreciative of that - thanks!
>
> Cocoon2 is an industrial-quality product, both in design and
> implementation. Ignoring for past experiences is not only blind, is
> plain stupid.
I know, that is why I am here listening (mostly :). Some things I like, some
I don't. Are you calling me stupid? :)
>
> At the same time, Cocoon1 is *still* used in heavy loaded production
> sites and makes me think that if such a limited architecture could reach
> that point, what will we do with Cocoon2?
>
> I'm so excited to see this :)
>
> > I wonder if cocoon is bloatware, at least for my needs.
>
> Cocoon includes many things and, granted, more that you need. It's more
> or less like PHP but with more modern design concepts (not that PHP is
> not modern, it's very cool indeed!, but lacks the concept of SoC right
> into the HTML+script design concept!).
>
> And for sure it's big: it is reaching the point where we have more java
> code in Cocoon than in the entire JDK! and that sums up to hundreds of
> thousands of lines of code!!! and written in a few years! Apache has
> more productivity of good quality java code than Sun itself!
>
> And if that was not enough, the community is one of the most active and,
> even better, it seems to be magnetically attracting other efforts as
> well (FOP, Batik, XIndice, POI, DELI) and triggering lots of
> cross-pollination in beween the ASF efforts (avalon, xalan, gump,
> forrest).
>
> > When working with a
> > small team (say 5-10 people spread out all over the world, well, US and
> > England) servlets and xslt/xml seem to do everything I need.
>
> Hey, if that works for you, great. But the fact that you stick around
> here seems to suggest that you find our input useful. So, I would
> suggest not to discard the software that was distilled after that input
> :)
Oh, I'm not. I am just being more careful this time. Once bitten, twice shy.
>
> > They work on
> > it dynamicially and then generate it as a static site whenever they
want.
> > And I would bet there are few people who can create a large
content-based
> > site faster.
>
> Never say never.
I never did :)
>
> > My sites (large publishing companies) are perhaps well-suited
> > to this though and other sites are perhaps better suited to cocoon.
> >
> > Why scoff something that works?
> > Why is it a bad thing?
>
> Never said that.
never say never :) OK
>
> My only point is: how do you know if your stuff is any better than
> cocoon2 since you didn't even try it?
I just downloaded it about an hour or two ago.
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Understanding cocoon ......
Posted by Stefano Mazzocchi <st...@apache.org>.
Robert Koberg wrote:
>
> Hello,
>
> > ----- Original Message -----
> > From: "Stefano Mazzocchi" <st...@apache.org>
> > Christoph Henrici wrote:
> > >
> > > I have been studying, testing and playing around with cocoon in the
> > > last few days as a newcomer : i am greatly impressed with what ease with
> > > cocoon "pipelines" arbrary data sources can be "chained" to a result
> > > target: a very powerful paradigm (pipe) applied in a powerful context
> > > (http) by using great technology (xml, xlst).
> >
> > Yep, I think you really hit the point. Some people believe that it's
> > enough to add server side transformation capabilities (say, adding a
> > XSLT post-processor as a servlet filter!) to come up with a publishing
> > framework.
>
> I guess I am one of those :) But I guess you are talking about much broader
> publishing needs. It is all relative.
Oh, yes. I was not referring to ad-hoc solutions but to who wants to
take a publishing system (say Turbine), add an XML transformation
language on top (say DVSL*) and voila': who needs Cocoon?
(*) http://jakarta.apache.org/velocity/dvsl/index.html
> I have not used cocoon2 yet. I had very bad experiences adopting cocoon1
> (right when it came out -- MacMillan's idiotsguides.com - god, I wish I
> could take that one back :( for many things besides cocoon's PIs - my first
> "real" web-site...). When I understand what I needed (too late) I realized
> that cocoon was the furthest thing. I am hoping to gather this info about
> cocoon2 from you guys (and maybe throw my 2cents in every now and then :).
> It sounds like you have a fantastic product. I would have installed it to
> play around with but all the other things you need... Then again, all the
> buzz makes it very interesting.
I've talked with many people that were scared away by Cocoon1. No excuse
there: it was a first try and a pretty home-made one. But considering
that the XML model is not yet finished, the XML spec is 4 years old and
Cocoon is 3 years old, I think that we did have a good excuse to try
things out.
Cocoon2 is an industrial-quality product, both in design and
implementation. Ignoring for past experiences is not only blind, is
plain stupid.
At the same time, Cocoon1 is *still* used in heavy loaded production
sites and makes me think that if such a limited architecture could reach
that point, what will we do with Cocoon2?
I'm so excited to see this :)
> I wonder if cocoon is bloatware, at least for my needs.
Cocoon includes many things and, granted, more that you need. It's more
or less like PHP but with more modern design concepts (not that PHP is
not modern, it's very cool indeed!, but lacks the concept of SoC right
into the HTML+script design concept!).
And for sure it's big: it is reaching the point where we have more java
code in Cocoon than in the entire JDK! and that sums up to hundreds of
thousands of lines of code!!! and written in a few years! Apache has
more productivity of good quality java code than Sun itself!
And if that was not enough, the community is one of the most active and,
even better, it seems to be magnetically attracting other efforts as
well (FOP, Batik, XIndice, POI, DELI) and triggering lots of
cross-pollination in beween the ASF efforts (avalon, xalan, gump,
forrest).
> When working with a
> small team (say 5-10 people spread out all over the world, well, US and
> England) servlets and xslt/xml seem to do everything I need.
Hey, if that works for you, great. But the fact that you stick around
here seems to suggest that you find our input useful. So, I would
suggest not to discard the software that was distilled after that input
:)
> They work on
> it dynamicially and then generate it as a static site whenever they want.
> And I would bet there are few people who can create a large content-based
> site faster.
Never say never.
> My sites (large publishing companies) are perhaps well-suited
> to this though and other sites are perhaps better suited to cocoon.
>
> Why scoff something that works?
> Why is it a bad thing?
Never said that.
My only point is: how do you know if your stuff is any better than
cocoon2 since you didn't even try it?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Understanding cocoon ......
Posted by Robert Koberg <ro...@koberg.com>.
Hello,
> ----- Original Message -----
> From: "Stefano Mazzocchi" <st...@apache.org>
> Christoph Henrici wrote:
> >
> > I have been studying, testing and playing around with cocoon in the
> > last few days as a newcomer : i am greatly impressed with what ease with
> > cocoon "pipelines" arbrary data sources can be "chained" to a result
> > target: a very powerful paradigm (pipe) applied in a powerful context
> > (http) by using great technology (xml, xlst).
>
> Yep, I think you really hit the point. Some people believe that it's
> enough to add server side transformation capabilities (say, adding a
> XSLT post-processor as a servlet filter!) to come up with a publishing
> framework.
I guess I am one of those :) But I guess you are talking about much broader
publishing needs. It is all relative.
I have not used cocoon2 yet. I had very bad experiences adopting cocoon1
(right when it came out -- MacMillan's idiotsguides.com - god, I wish I
could take that one back :( for many things besides cocoon's PIs - my first
"real" web-site...). When I understand what I needed (too late) I realized
that cocoon was the furthest thing. I am hoping to gather this info about
cocoon2 from you guys (and maybe throw my 2cents in every now and then :).
It sounds like you have a fantastic product. I would have installed it to
play around with but all the other things you need... Then again, all the
buzz makes it very interesting.
I wonder if cocoon is bloatware, at least for my needs. When working with a
small team (say 5-10 people spread out all over the world, well, US and
England) servlets and xslt/xml seem to do everything I need. They work on
it dynamicially and then generate it as a static site whenever they want.
And I would bet there are few people who can create a large content-based
site faster. My sites (large publishing companies) are perhaps well-suited
to this though and other sites are perhaps better suited to cocoon.
Why scoff something that works?
Why is it a bad thing?
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Understanding cocoon ......
Posted by Stefano Mazzocchi <st...@apache.org>.
Christoph Henrici wrote:
>
> I have been studying, testing and playing around with cocoon in the
> last few days as a newcomer : i am greatly impressed with what ease with
> cocoon "pipelines" arbrary data sources can be "chained" to a result
> target: a very powerful paradigm (pipe) applied in a powerful context
> (http) by using great technology (xml, xlst).
Yep, I think you really hit the point. Some people believe that it's
enough to add server side transformation capabilities (say, adding a
XSLT post-processor as a servlet filter!) to come up with a publishing
framework.
But without a solid and well designed internal component architecture
this is definately not true.
> In context of the
> development of a web based application with requirements for a fairly
> generic mechanism for the dynamic personlization of webpages in terms of
> content and style the following questions below arised. Maybe they stem
> from the fact, that i still missed a couple of aspect and points, maybe
> the requirement or idea is just not thought through enough, anyway:
>
> a. Is it possible to "compose" pipelines and having the composed
> pipeline beeing processing bottom-up and the whole beeing rendered for
> example as html: A compostion of tables within table, frames within
> frame etc., where the content of the "elementary" pipelines are
> dyanmic, taking for examples data from the databases. I am aware that
> the aggregation <map:aggregate> mechansim provides a somewhat similiar
> construction, only the composition could also be composed of aggregations.
There are two 'flavors' of aggregation in Cocoon: generation-based and
transformation-based.
The first is done with the use of the <aggregate> semantic include in
the sitemap. In fact, an aggregator is nothing but a special generator,
but it was decided to place directly into the sitemap semantics since it
is very useful.
The problem with this approach is that the parts must be defined at
sitemap-design time. While this normally covers 90% of the cases, in
some other cases (my-netscape-like portal applications, for example) the
aggregation is driven by environment information (say: user preferences)
thus cannot be specified in the sitemap (unless everything is aggregated
and then filtered out, but this is not performant at all, expecially for
very complex portals).
For this reason, another solution is present, which is based on
server-side xinclude expansion performed at a transformation stage.
In short: the pipeline contains some namespaces that indicate 'include'
behavior and the transformer acts as an aggregator but on 'part'
information which is previously generated, so might come from any
source.
it is easy to imagine a generator that gets the details about the user
preferences out of a session bean (or ejb, database, file, whatever) and
streams them on the pipe, letting the subsequent transformer performing
the aggregation.
of course, all this is cache-aware.
> b. Is it possible the change the sitemap or more specifically the
> piplines configuration ( <map:pipelines>) dynamically.
No and I will continue to veto it until somebody changes my mind.
I think dynamic pipelines are *bad* and so far, nobody was able to come
up with a meaningful example that *required* dynamic pipelines and
couln't be done with better pipeline components.
> If this can be achieved with cocoon 2 i would be very grateful for a
> rough outline on how.
Check the XIncludeTransformer and the CIncludeTransformer.
> If some additional development would be needed it
> would be great to have some starting hints at where to start looking at.
> Any other ideas or suggestions with regard to the requirement are also
> greatly appreciated.
Hope this helps.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Understanding cocoon ......
Posted by Luca Morandini <l....@tin.it>.
Christoph,
Just my 1.2c (after tax)...
> a. Is it possible to "compose" pipelines and having the composed
> pipeline beeing processing bottom-up and the whole beeing rendered for
> example as html: A compostion of tables within table, frames within
> frame etc., where the content of the "elementary" pipelines are
> dyanmic, taking for examples data from the databases. I am aware that
> the aggregation <map:aggregate> mechansim provides a somewhat similiar
> construction, only the composition could also be composed of aggregations.
Well, not exaclty what you're asking for, but... you can, for instance, feed
data produced by Cocoon inside an XSL using the "cocoon:" prefix, like in:
<xsl:copy-of select="document('cocoon:/b.xml')"/>
Where b.xml can be the output of a pipeline (including aggregation).
> b. Is it possible the change the sitemap or more specifically the
> piplines configuration ( <map:pipelines>) dynamically.
No, unless you rewrite (outside Cocoon) the sitemap.xmap and recompile it
every time... daunting indeed.
Best regards,
---------------------------------------------
Luca Morandini
GIS Consultant
lmorandini@ieee.org
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
> -----Original Message-----
> From: Christoph Henrici [mailto:chenrici@dplanet.ch]
> Sent: Wednesday, January 09, 2002 9:41 PM
> To: cocoon-users@xml.apache.org; cocoon-dev@xml.apache.org
> Subject: Understanding cocoon ......
>
>
> I have been studying, testing and playing around with cocoon in the
> last few days as a newcomer : i am greatly impressed with what ease with
> cocoon "pipelines" arbrary data sources can be "chained" to a result
> target: a very powerful paradigm (pipe) applied in a powerful context
> (http) by using great technology (xml, xlst). In context of the
> development of a web based application with requirements for a fairly
> generic mechanism for the dynamic personlization of webpages in terms of
> content and style the following questions below arised. Maybe they stem
> from the fact, that i still missed a couple of aspect and points, maybe
> the requirement or idea is just not thought through enough, anyway:
>
> a. Is it possible to "compose" pipelines and having the composed
> pipeline beeing processing bottom-up and the whole beeing rendered for
> example as html: A compostion of tables within table, frames within
> frame etc., where the content of the "elementary" pipelines are
> dyanmic, taking for examples data from the databases. I am aware that
> the aggregation <map:aggregate> mechansim provides a somewhat similiar
> construction, only the composition could also be composed of aggregations.
> b. Is it possible the change the sitemap or more specifically the
> piplines configuration ( <map:pipelines>) dynamically.
>
> If this can be achieved with cocoon 2 i would be very grateful for a
> rough outline on how. If some additional development would be needed it
> would be great to have some starting hints at where to start looking at.
> Any other ideas or suggestions with regard to the requirement are also
> greatly appreciated.
>
> Christoph Henrici
>
>
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: Understanding cocoon ......
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Christoph Henrici [mailto:chenrici@dplanet.ch]
>
> I have been studying, testing and playing around with cocoon in the
> last few days as a newcomer : i am greatly impressed with what ease
with
> cocoon "pipelines" arbrary data sources can be "chained" to a result
> target: a very powerful paradigm (pipe) applied in a powerful context
> (http) by using great technology (xml, xlst). In context of the
> development of a web based application with requirements for a fairly
> generic mechanism for the dynamic personlization of webpages in terms
of
> content and style the following questions below arised. Maybe they
stem
> from the fact, that i still missed a couple of aspect and points,
maybe
> the requirement or idea is just not thought through enough, anyway:
>
> a. Is it possible to "compose" pipelines and having the composed
> pipeline beeing processing bottom-up and the whole beeing rendered for
> example as html: A compostion of tables within table, frames within
> frame etc., where the content of the "elementary" pipelines are
> dyanmic, taking for examples data from the databases. I am aware that
> the aggregation <map:aggregate> mechansim provides a somewhat similiar
> construction, only the composition could also be composed of
aggregations.
I'm not sure I understood you correctly... But, if you want to aggregate
resources and do not know at the moment of writing sitemap what to
aggregate - then you can use "include" capabilities of Cocoon. It is
possible to do:
<map:generate/> to generate document with include tags (this can be from
database),
<map:transform type="cinclude"/> (or xinclude) - processed include tags
and includes content from the sources mentioned in these tags,
<map:serialize/> serializes results.
See http://xml.apache.org/cocoon/userdocs/transformers/transformers.html
for documentation on xinclude and cinclude transformers.
> b. Is it possible the change the sitemap or more specifically the
> piplines configuration ( <map:pipelines>) dynamically.
No, this is not possible.
Regards,
Vadim
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>