RE: Using the results of an aggregate part.

2003-02-06 Thread Hunsberger, Peter
 Now the question raises, how i can gather an xml-fragment,
 put it into some temporary place (ideally in memory) and
 refer to this fragement from another part of the pipeline.

Any reason why you don't trust Cocoon caching to do this for you?  From the
looks of what you've shown us there are no request or client side parameters
going into the fragment generation and it should therefore be possible to
have it always cached once it has been created the first time? 




-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Using the results of an aggregate part.

2003-01-29 Thread SAXESS - Hussayn Dabbous
thats interesting...

i got a similar usecase yesterday:

o An application can be asked to give away some configuration
  parameters in an XML stream. i.e a list of search engines
  with names, links, search-parameter-descriptors and so on.
o now i ask my application once for the config
  to get the list of search engines. then i create a search
  engine-selector (using an xsl transform)
o then i ask my application to deliver the data for the
  currently selected search-engine. i use a different
  xslt to build the inputmask for the engine.
o finally i take the results and bundle them to
  the final page with just another xslt.

assume, the application can't be changed, then i am forced to
either create a transformer for search-engine-selector + input-mask
that does not use aggregation, or i have to call my app twice,
getting back the same data twice and transforming it differently.

If it where possible to call the application once, then apply
two map:part to the result, this would help enormously in my
use case.

What i can think of is something like dropping the data to
a file, then aggregating from the file. that should be possible
in one call, but how could that be done ?

regards, hussayn


Geoff Howard wrote:

At first glance, this does not look very natural in Cocoon, but I don't
think there's enough information given to advise you.  What needs to happen
in the rest of the pipeline?  Are you truly aggregating the content of those
two items, or are you merely trying to use the aggregate feature to trigger
the two pipelines in order?  What does each individual pipeline do/return?

Geoff

-Original Message-
From: Joe Latty [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 5:42 PM
To: Cocoon Users
Subject: Using the results of an aggregate part.


Greetings

Firstly I should warn you I am a complete newbie.

On the following url http://wiki.cocoondev.org/Wiki.jsp?page=Aggregator I
found this quote:

(Aggregator) Allows the combination of multiple XML documents. An
individual aggregator contains one or more parts. Each part is a document
fragment, these become children of a new document root, whose element name
is defined by an attribute on the aggregator.

I am trying to get the results from one part and use these to obtain the
correct results from the second part.

map:aggregate element=site
  map:part src=cocoon:/getSomeDataFromACall.xml/ !--
and put the result in the session --
  map:part src=cocoon:/toUseToObtainDetailsFromThisCall.xml/  !-- using
the data in the session object --
/map:aggregate

Is this possible?

Is the aggregator the place to be looking?

Is there a simple way to do this?

Thanks for any help.

Joe


-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]



--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]