RE: pipeline dependencies

2003-06-20 Thread Carmona Perez, David
Create a simple selector to check if the file exists, and if it doesn't call pipeline 
A.


David

-Mensaje original-
De: Ali Mesbah [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 19 de junio de 2003 14:10
Para: [EMAIL PROTECTED]
Asunto: pipeline dependencies

Hi,
Is it possible to define pipeline dependencies in the sitemap?

Imagine I have two pipelines A and B.
Pipeline B has a SourceWritingTransformer and all it does is writing a generated
document on the filesystem.
Pipeline A has its own generator and transformer but it depends on the document
written by B. So A denpends on B. In other words when A is called B has to be
called first but the output of A sould be serialized to the browser (and not the
output of B).


Thanks,
Ali


--
-- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600

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

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



Re: pipeline dependencies

2003-06-20 Thread Ali Mesbah
As quoted from Upayavira [EMAIL PROTECTED]:
  Is it possible to define pipeline dependencies in the sitemap? 
  
  Imagine I have two pipelines A and B. 
  Pipeline B has a SourceWritingTransformer and all it does is writing a
  generated document on the filesystem. Pipeline A has its own generator
  and transformer but it depends on the document written by B. So A
  denpends on B. In other words when A is called B has to be called
  first but the output of A sould be serialized to the browser (and not
  the output of B).
 
 You could try just including pipeline B in with pipeline A using cocoon:, e.g.
 
 map:match pattern=B
   map:generate...
   map:transform type=SWT
   map:serialize type=xml/
 /map:match
 
 map:match pattern=A
   map:aggregate element=foo
 map:part src=cocoon:/B/
 map:part src=a-src.xml/
   /map:aggregate
   map:transform...
   map:serialize...
 /map:match
 
 If you can get pipeline B to cache, then it will only write if the source of that 
 pipeline 
 has changed.
 
 Then, if necessary, you can ignore the aggregated output from pipeline B, but it is 
 just 
 there to enforce the dependency.
 
 All depends upon the caching of the SourceWritingTransformer. 
 

Thanks Upayavira. 
I think with the current implementation that is the only
possible way of doing it. Although it's not efficient (you dont actually want to
aggregate), it serves the purpose.



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

-- 
-- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600

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



Re: pipeline dependencies

2003-06-20 Thread Upayavira
  If you can get pipeline B to cache, then it will only write if the
  source of that pipeline has changed.
  
  Then, if necessary, you can ignore the aggregated output from
  pipeline B, but it is just there to enforce the dependency.
  
  All depends upon the caching of the SourceWritingTransformer. 

 Thanks Upayavira. 
 I think with the current implementation that is the only
 possible way of doing it. Although it's not efficient (you dont
 actually want to aggregate), it serves the purpose.

Another way you can do it is read your original content from disc, then transform it 
into something like:

xml
  source:write
contentBlah/content
  /source:write
  contentBlah/content
/xml

This way you repeat your content twice, once to go into the SWT, and once to go on 
to the output. Your following transformer then just strips out any nodes in the SWT 
namespace.

Make sense?

Can you explain a little more _why_ you want to be writing to disk? That'll help me 
understand how best you can achieve your requirements.

Regards, Upayavira


map:match ...
  map:generate src=original source
  map:transform src=make_

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



Re: pipeline dependencies

2003-06-20 Thread Ali Mesbah
As quoted from Upayavira [EMAIL PROTECTED]:
 Another way you can do it is read your original content from disc, then transform it 
 into something like:
 
 xml
   source:write
 contentBlah/content
   /source:write
   contentBlah/content
 /xml
 
 This way you repeat your content twice, once to go into the SWT, and once to go on 
 to the output. Your following transformer then just strips out any nodes in the SWT 
 namespace.
 
 Make sense?
 
 Can you explain a little more _why_ you want to be writing to disk? That'll help me 
 understand how best you can achieve your requirements.

The thing is I generate a stylesheet in B which is used in A (and in other
pipelines):

match pattern=B
  map:generate src=resources/{filename}.xml/
  map:transform src=styles/Meta_output.xsl/
  map:serialize type=xml/
/map:match

Note that the output of B is a stylesheet (say output.xsl).

Then the first thing that comes to mind is using the Cocoon protocol to read
this output.xsl as the src of the transformer in A:

match pattern=A
  map:generate src=resources/bla.xml/
  map:transform src=cocoon:/B/
  map:serialize type=html/
/map:match
  
But unfortunately this does not work. (I have posted messages on this matter a
few days ago). The output of A is not what it should be at all. 

So I thought a workaround is to write the output.xsl to file and then read it in
A. But then I had the issue of dependencies

I hope i have been clear enough. By the way have you ever tried to use cocoon:/
as the src of a Transformer?

Thanks,
Ali

 Regards, Upayavira
 
 
 map:match ...
   map:generate src=original source
   map:transform src=make_
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-- 
-- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600

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



Re: pipeline dependencies

2003-06-20 Thread Upayavira
 The thing is I generate a stylesheet in B which is used in A (and in
 other pipelines):
 
 match pattern=B
   map:generate src=resources/{filename}.xml/
   map:transform src=styles/Meta_output.xsl/
   map:serialize type=xml/
 /map:match
 
 Note that the output of B is a stylesheet (say output.xsl).
 
 Then the first thing that comes to mind is using the Cocoon protocol
 to read this output.xsl as the src of the transformer in A:
 
 match pattern=A
   map:generate src=resources/bla.xml/
   map:transform src=cocoon:/B/
   map:serialize type=html/
 /map:match
 
 But unfortunately this does not work. (I have posted messages on this
 matter a few days ago). The output of A is not what it should be at
 all. 
 
 So I thought a workaround is to write the output.xsl to file and then
 read it in A. But then I had the issue of dependencies
 
 I hope i have been clear enough. By the way have you ever tried to use
 cocoon:/ as the src of a Transformer?

Ah. Much clearer now. No you shouldn't use the SWT to do this - you should be able 
to rely upon Cocoon's caching to worry about that for you.

Yes, you can access stylesheets using the cocoon: protocol. No I haven't done it yet, 
but I will need to do so soon.

So, when you say you tried it and it doesn't work, what doesn't work? What happens?

Also, what version of Cocoon are you using?

Regards, Upayavira




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



Re: pipeline dependencies

2003-06-20 Thread Ali Mesbah
As quoted from Upayavira [EMAIL PROTECTED]:
 Ali,
 
 Have you seen:
 
 http://wiki.cocoondev.org/Wiki.jsp?page=MetaStylesheets
 
 Maybe that'll help.

It works indeed. I see what I was doing wrong; 
In my Meta_output at some places I had something like:

xsl:text disable-output-escaping=yes
  lt;xsl:apply-templatesgt;
lt;xsl:with-param name=path select=$root/gt;
  lt;/xsl:apply-templatesgt;
/xsl:text

This works if you save the output on filesystem and read it again but not using
it directly via Cocoon protocol. The trick is to create elements explicitely instead 
of using xsl:text:

xsl:element name=xsl:apply-templates
  xsl:element name=xsl:with-param
xsl:attribute name=namepath/xsl:attribute
xsl:attribute name=select
  xsl:text$root/xsl:text
/xsl:attribute 
  /xsl:element
/xsl:element

Thanks Upayavira for helping out,

Ali

 Regards, Upayavira
 
 On 20 Jun 2003 at 11:16, Ali Mesbah wrote:
 
  As quoted from Upayavira [EMAIL PROTECTED]:
   Another way you can do it is read your original content from disc,
   then transform it into something like:
   
   xml
 source:write
   contentBlah/content
 /source:write
 contentBlah/content
   /xml
   
   This way you repeat your content twice, once to go into the SWT, and
   once to go on to the output. Your following transformer then just
   strips out any nodes in the SWT namespace.
   
   Make sense?
   
   Can you explain a little more _why_ you want to be writing to disk?
   That'll help me understand how best you can achieve your
   requirements.
  
  The thing is I generate a stylesheet in B which is used in A (and in
  other pipelines):
  
  match pattern=B
map:generate src=resources/{filename}.xml/
map:transform src=styles/Meta_output.xsl/
map:serialize type=xml/
  /map:match
  
  Note that the output of B is a stylesheet (say output.xsl).
  
  Then the first thing that comes to mind is using the Cocoon protocol
  to read this output.xsl as the src of the transformer in A:
  
  match pattern=A
map:generate src=resources/bla.xml/
map:transform src=cocoon:/B/
map:serialize type=html/
  /map:match
  
  But unfortunately this does not work. (I have posted messages on this
  matter a few days ago). The output of A is not what it should be at
  all. 
  
  So I thought a workaround is to write the output.xsl to file and then
  read it in A. But then I had the issue of dependencies
  
  I hope i have been clear enough. By the way have you ever tried to use
  cocoon:/ as the src of a Transformer?
  
  Thanks,
  Ali
  
   Regards, Upayavira
   
   
   map:match ...
 map:generate src=original source
 map:transform src=make_
   
   
   - To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  -- 
  -- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED] For
  additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-- 
-- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600

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



pipeline dependencies

2003-06-19 Thread Ali Mesbah
Hi,
Is it possible to define pipeline dependencies in the sitemap? 

Imagine I have two pipelines A and B. 
Pipeline B has a SourceWritingTransformer and all it does is writing a generated
document on the filesystem. 
Pipeline A has its own generator and transformer but it depends on the document
written by B. So A denpends on B. In other words when A is called B has to be
called first but the output of A sould be serialized to the browser (and not the
output of B).


Thanks,
Ali


-- 
-- Ali Mesbah, West Consulting B.V., www.west.nl, +31 15 2191600

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



Re: pipeline dependencies

2003-06-19 Thread Upayavira
 Is it possible to define pipeline dependencies in the sitemap? 
 
 Imagine I have two pipelines A and B. 
 Pipeline B has a SourceWritingTransformer and all it does is writing a
 generated document on the filesystem. Pipeline A has its own generator
 and transformer but it depends on the document written by B. So A
 denpends on B. In other words when A is called B has to be called
 first but the output of A sould be serialized to the browser (and not
 the output of B).

You could try just including pipeline B in with pipeline A using cocoon:, e.g.

map:match pattern=B
  map:generate...
  map:transform type=SWT
  map:serialize type=xml/
/map:match

map:match pattern=A
  map:aggregate element=foo
map:part src=cocoon:/B/
map:part src=a-src.xml/
  /map:aggregate
  map:transform...
  map:serialize...
/map:match

If you can get pipeline B to cache, then it will only write if the source of that 
pipeline 
has changed.

Then, if necessary, you can ignore the aggregated output from pipeline B, but it is 
just 
there to enforce the dependency.

All depends upon the caching of the SourceWritingTransformer. 

I may well be off track here...

Regards, Upayavira


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



RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-14 Thread Eisert, Wolfram

Hi David,

yesterday I send a patch to cocoon-dev (which now was applied to 20-branch)
which should solve your problem.

See
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100827658927876w=2
for details.

Wolfram

 -Urspr√ľngliche Nachricht-
 Von: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
 Gesendet am: Mittwoch, 12. Dezember 2001 17:49
 An: [EMAIL PROTECTED]
 Betreff: RE: XSP page getting called TWICE! (was: Pipeline 
 dependencies)
 
 Ah, but that's the rub.  It's only invoked in one place in 
 the Java code, and yet it gets called twice.
 
 Cocoon itself is calling this pipeline twice, for some 
 reason, and I have no idea why.
 
 Thanks for the msg, though.
 
 
 DR
 
 
 At 10:04 AM 12/12/01 +0100, you wrote:
 David,
 
 I think what Mitch meant and I'm not sure you mean the same - you may
 trace down from which point of sitemap_xmap.java your pipelines are
 invoked. And as soon you found _two_ places of invocation in 
 java code,
 you may match them back to your sitemap.xmap (you should see what
 exactly made your matcher to be invoked twice).
 
 Best wishes,
 Nick
 
   -Original Message-
   From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] 
   Sent: Wednesday, December 12, 2001 12:01 AM
   To: [EMAIL PROTECTED]
   Subject: RE: XSP page getting called TWICE! (was: Pipeline 
   dependencies)
   
   
   I did.  From the trace, it seems like the whole map:match 
   pattern=rtf_merge_data pipeline is getting run twice - 
   which I found even more confusing.
   
   Not sure why it should need to run that pipeline twice.  
   Clearly that's happening because of some combination of:  a) 
   it's an internal pipeline, b) I'm using the results of that 
   pipeline in a transform in another pipeline.
   
   I can't figure out for the life of me why it should be run 
   twice though.
   
   Thanks for giving it a shot though and please let me know if 
   you have any other suggestions, as I still haven't solved this.
   
   
   DR
   
   
   
   
   
   At 08:58 AM 12/11/01 -0800, you wrote:
   Have you tried modifying the code to print a stack trace 
 with each 
   invocation?  This might help isolate the source of each call.
   
   -Mitch
   
   -Original Message-
   From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
   Sent: Tuesday, December 11, 2001 7:37 AM
   To: [EMAIL PROTECTED]
   Subject: Re: XSP page getting called TWICE! (was: Pipeline 
   dependencies)
   
   
   I posted this a couple of times here, as well as once to the 
   Dev list.  
   No one's written back with any suggestions so far.
   
   I hope y'all don't mind, but I'd like to post this one more 
   time.  It's 
   really stumping me!  Please help!
   
   ==
   
   Anyone have any thoughts on this?
   
   What could cause an XSP page to get called twice in the 
 same request?
   
   Tnx!
   
   DR
   
   
   At 12:07 PM 12/7/01 -0500, you wrote:
Actually, regarding the setup below (which I mentioned 
 in another 
message),
   I'm having a problem with it and would appreciate some help.

Take a look at the sitemap segment below.  And let me 
 clarify it a 
bit too:

The XSL stylesheet that I'm using in the transform on 
pd/mergedoc.html is
   generated *dynamically*, from an xsp page 
   (pages/gen_merge_xsl.xsp).

This is working just fine, except for one small problem:

For some reason, on each request, this XSP page is getting 
   executed 
TWICE!
   Although this doesn't technically cause any errors, it's pretty 
   inefficient since it hits the database twice, generates the 
   xsl twice, 
   etc.

Any ideas why?

Some possible thoughts I had:

* perhaps the internal-only=true is causing this?

* perhaps an additional aspect of this setup is 
 causing this:  the
   cocoon:/rtf_parse generation step (not listed) is setting an 
   attachment response header (Content-Disposition: attachment; 
   filename=myfile.rtf) so that the file will be 
 downloaded instead of 
   displayed directly in the browser.  Could that be causing this?

Any help appreciated!

TIA!


DR


At 11:17 AM 12/7/01 -0500, you wrote:
 It is possible.  I'm using that in my site:
 
 map:pipeline
   map:match pattern=pd/mergedoc.html
   map:generate src=cocoon:/rtf_parse/
   map:transform 
 src=cocoon:/rtf_merge_data/
   map:serialize type=rtf/
   /map:match
 /map:pipeline
 
 
 map:pipeline internal-only=true
   map:match pattern=rtf_merge_data
   map:generate type=serverpages
   src=pages/gen_merge_xsl.xsp/
   map:serialize type=xml/
   /map:match
 /map:pipeline
 
 
 DR
   
   
   
 -
   Please check that your

RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-14 Thread David Rosenstrauch

Wow - sweet!

Unfortunately I didn't get a quick response on the dev mailing list, and unsubscribed 
before I saw your post.

Thanks very much for taking care of this Wolfram!


DR


At 11:39 AM 12/14/01 +0100, you wrote:
Hi David,

yesterday I send a patch to cocoon-dev (which now was applied to 20-branch)
which should solve your problem.

See
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100827658927876w=2
for details.

Wolfram

  -Urspr√ľngliche Nachricht-
  Von: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
  Gesendet am: Mittwoch, 12. Dezember 2001 17:49
  An: [EMAIL PROTECTED]
  Betreff: RE: XSP page getting called TWICE! (was: Pipeline 
  dependencies)
  
  Ah, but that's the rub.  It's only invoked in one place in 
  the Java code, and yet it gets called twice.
  
  Cocoon itself is calling this pipeline twice, for some 
  reason, and I have no idea why.
  
  Thanks for the msg, though.
  
  
  DR
  
  
  At 10:04 AM 12/12/01 +0100, you wrote:
  David,
  
  I think what Mitch meant and I'm not sure you mean the same - you may
  trace down from which point of sitemap_xmap.java your pipelines are
  invoked. And as soon you found _two_ places of invocation in 
  java code,
  you may match them back to your sitemap.xmap (you should see what
  exactly made your matcher to be invoked twice).
  
  Best wishes,
  Nick
  
-Original Message-
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 12, 2001 12:01 AM
To: [EMAIL PROTECTED]
Subject: RE: XSP page getting called TWICE! (was: Pipeline 
dependencies)


I did.  From the trace, it seems like the whole map:match 
pattern=rtf_merge_data pipeline is getting run twice - 
which I found even more confusing.

Not sure why it should need to run that pipeline twice.  
Clearly that's happening because of some combination of:  a) 
it's an internal pipeline, b) I'm using the results of that 
pipeline in a transform in another pipeline.

I can't figure out for the life of me why it should be run 
twice though.

Thanks for giving it a shot though and please let me know if 
you have any other suggestions, as I still haven't solved this.


DR





At 08:58 AM 12/11/01 -0800, you wrote:
Have you tried modifying the code to print a stack trace 
  with each 
invocation?  This might help isolate the source of each call.

-Mitch

-Original Message-
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: XSP page getting called TWICE! (was: Pipeline 
dependencies)


I posted this a couple of times here, as well as once to the 
Dev list.  
No one's written back with any suggestions so far.

I hope y'all don't mind, but I'd like to post this one more 
time.  It's 
really stumping me!  Please help!

==

Anyone have any thoughts on this?

What could cause an XSP page to get called twice in the 
  same request?

Tnx!

DR


At 12:07 PM 12/7/01 -0500, you wrote:
 Actually, regarding the setup below (which I mentioned 
  in another 
 message),
I'm having a problem with it and would appreciate some help.
 
 Take a look at the sitemap segment below.  And let me 
  clarify it a 
 bit too:
 
 The XSL stylesheet that I'm using in the transform on 
 pd/mergedoc.html is
generated *dynamically*, from an xsp page 
(pages/gen_merge_xsl.xsp).
 
 This is working just fine, except for one small problem:
 
 For some reason, on each request, this XSP page is getting 
executed 
 TWICE!
Although this doesn't technically cause any errors, it's pretty 
inefficient since it hits the database twice, generates the 
xsl twice, 
etc.
 
 Any ideas why?
 
 Some possible thoughts I had:
 
 * perhaps the internal-only=true is causing this?
 
 * perhaps an additional aspect of this setup is 
  causing this:  the
cocoon:/rtf_parse generation step (not listed) is setting an 
attachment response header (Content-Disposition: attachment; 
filename=myfile.rtf) so that the file will be 
  downloaded instead of 
displayed directly in the browser.  Could that be causing this?
 
 Any help appreciated!
 
 TIA!
 
 
 DR
 
 
 At 11:17 AM 12/7/01 -0500, you wrote:
  It is possible.  I'm using that in my site:
  
  map:pipeline
map:match pattern=pd/mergedoc.html
map:generate src=cocoon:/rtf_parse/
map:transform 
  src=cocoon:/rtf_merge_data/
map:serialize type=rtf/
/map:match
  /map:pipeline

RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-12 Thread Nick Entin

David,

I think what Mitch meant and I'm not sure you mean the same - you may
trace down from which point of sitemap_xmap.java your pipelines are
invoked. And as soon you found _two_ places of invocation in java code,
you may match them back to your sitemap.xmap (you should see what
exactly made your matcher to be invoked twice).

Best wishes,
Nick

 -Original Message-
 From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] 
 Sent: Wednesday, December 12, 2001 12:01 AM
 To: [EMAIL PROTECTED]
 Subject: RE: XSP page getting called TWICE! (was: Pipeline 
 dependencies)
 
 
 I did.  From the trace, it seems like the whole map:match 
 pattern=rtf_merge_data pipeline is getting run twice - 
 which I found even more confusing.
 
 Not sure why it should need to run that pipeline twice.  
 Clearly that's happening because of some combination of:  a) 
 it's an internal pipeline, b) I'm using the results of that 
 pipeline in a transform in another pipeline.
 
 I can't figure out for the life of me why it should be run 
 twice though.
 
 Thanks for giving it a shot though and please let me know if 
 you have any other suggestions, as I still haven't solved this.
 
 
 DR
 
 
 
 
 
 At 08:58 AM 12/11/01 -0800, you wrote:
 Have you tried modifying the code to print a stack trace with each 
 invocation?  This might help isolate the source of each call.
 
 -Mitch
 
 -Original Message-
 From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, December 11, 2001 7:37 AM
 To: [EMAIL PROTECTED]
 Subject: Re: XSP page getting called TWICE! (was: Pipeline 
 dependencies)
 
 
 I posted this a couple of times here, as well as once to the 
 Dev list.  
 No one's written back with any suggestions so far.
 
 I hope y'all don't mind, but I'd like to post this one more 
 time.  It's 
 really stumping me!  Please help!
 
 ==
 
 Anyone have any thoughts on this?
 
 What could cause an XSP page to get called twice in the same request?
 
 Tnx!
 
 DR
 
 
 At 12:07 PM 12/7/01 -0500, you wrote:
  Actually, regarding the setup below (which I mentioned in another 
  message),
 I'm having a problem with it and would appreciate some help.
  
  Take a look at the sitemap segment below.  And let me clarify it a 
  bit too:
  
  The XSL stylesheet that I'm using in the transform on 
  pd/mergedoc.html is
 generated *dynamically*, from an xsp page 
 (pages/gen_merge_xsl.xsp).
  
  This is working just fine, except for one small problem:
  
  For some reason, on each request, this XSP page is getting 
 executed 
  TWICE!
 Although this doesn't technically cause any errors, it's pretty 
 inefficient since it hits the database twice, generates the 
 xsl twice, 
 etc.
  
  Any ideas why?
  
  Some possible thoughts I had:
  
  * perhaps the internal-only=true is causing this?
  
  * perhaps an additional aspect of this setup is causing this:  the
 cocoon:/rtf_parse generation step (not listed) is setting an 
 attachment response header (Content-Disposition: attachment; 
 filename=myfile.rtf) so that the file will be downloaded instead of 
 displayed directly in the browser.  Could that be causing this?
  
  Any help appreciated!
  
  TIA!
  
  
  DR
  
  
  At 11:17 AM 12/7/01 -0500, you wrote:
   It is possible.  I'm using that in my site:
   
   map:pipeline
 map:match pattern=pd/mergedoc.html
 map:generate src=cocoon:/rtf_parse/
 map:transform src=cocoon:/rtf_merge_data/
 map:serialize type=rtf/
 /map:match
   /map:pipeline
   
   
   map:pipeline internal-only=true
 map:match pattern=rtf_merge_data
 map:generate type=serverpages
 src=pages/gen_merge_xsl.xsp/
 map:serialize type=xml/
 /map:match
   /map:pipeline
   
   
   DR
 
 
 -
 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]
 
 -
 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]
 
 
 -
 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]
 
 


-
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

RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-12 Thread David Rosenstrauch

Ah, but that's the rub.  It's only invoked in one place in the Java code, and yet it 
gets called twice.

Cocoon itself is calling this pipeline twice, for some reason, and I have no idea why.

Thanks for the msg, though.


DR


At 10:04 AM 12/12/01 +0100, you wrote:
David,

I think what Mitch meant and I'm not sure you mean the same - you may
trace down from which point of sitemap_xmap.java your pipelines are
invoked. And as soon you found _two_ places of invocation in java code,
you may match them back to your sitemap.xmap (you should see what
exactly made your matcher to be invoked twice).

Best wishes,
Nick

  -Original Message-
  From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, December 12, 2001 12:01 AM
  To: [EMAIL PROTECTED]
  Subject: RE: XSP page getting called TWICE! (was: Pipeline 
  dependencies)
  
  
  I did.  From the trace, it seems like the whole map:match 
  pattern=rtf_merge_data pipeline is getting run twice - 
  which I found even more confusing.
  
  Not sure why it should need to run that pipeline twice.  
  Clearly that's happening because of some combination of:  a) 
  it's an internal pipeline, b) I'm using the results of that 
  pipeline in a transform in another pipeline.
  
  I can't figure out for the life of me why it should be run 
  twice though.
  
  Thanks for giving it a shot though and please let me know if 
  you have any other suggestions, as I still haven't solved this.
  
  
  DR
  
  
  
  
  
  At 08:58 AM 12/11/01 -0800, you wrote:
  Have you tried modifying the code to print a stack trace with each 
  invocation?  This might help isolate the source of each call.
  
  -Mitch
  
  -Original Message-
  From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
  Sent: Tuesday, December 11, 2001 7:37 AM
  To: [EMAIL PROTECTED]
  Subject: Re: XSP page getting called TWICE! (was: Pipeline 
  dependencies)
  
  
  I posted this a couple of times here, as well as once to the 
  Dev list.  
  No one's written back with any suggestions so far.
  
  I hope y'all don't mind, but I'd like to post this one more 
  time.  It's 
  really stumping me!  Please help!
  
  ==
  
  Anyone have any thoughts on this?
  
  What could cause an XSP page to get called twice in the same request?
  
  Tnx!
  
  DR
  
  
  At 12:07 PM 12/7/01 -0500, you wrote:
   Actually, regarding the setup below (which I mentioned in another 
   message),
  I'm having a problem with it and would appreciate some help.
   
   Take a look at the sitemap segment below.  And let me clarify it a 
   bit too:
   
   The XSL stylesheet that I'm using in the transform on 
   pd/mergedoc.html is
  generated *dynamically*, from an xsp page 
  (pages/gen_merge_xsl.xsp).
   
   This is working just fine, except for one small problem:
   
   For some reason, on each request, this XSP page is getting 
  executed 
   TWICE!
  Although this doesn't technically cause any errors, it's pretty 
  inefficient since it hits the database twice, generates the 
  xsl twice, 
  etc.
   
   Any ideas why?
   
   Some possible thoughts I had:
   
   * perhaps the internal-only=true is causing this?
   
   * perhaps an additional aspect of this setup is causing this:  the
  cocoon:/rtf_parse generation step (not listed) is setting an 
  attachment response header (Content-Disposition: attachment; 
  filename=myfile.rtf) so that the file will be downloaded instead of 
  displayed directly in the browser.  Could that be causing this?
   
   Any help appreciated!
   
   TIA!
   
   
   DR
   
   
   At 11:17 AM 12/7/01 -0500, you wrote:
It is possible.  I'm using that in my site:

map:pipeline
  map:match pattern=pd/mergedoc.html
  map:generate src=cocoon:/rtf_parse/
  map:transform src=cocoon:/rtf_merge_data/
  map:serialize type=rtf/
  /map:match
/map:pipeline


map:pipeline internal-only=true
  map:match pattern=rtf_merge_data
  map:generate type=serverpages
  src=pages/gen_merge_xsl.xsp/
  map:serialize type=xml/
  /map:match
/map:pipeline


DR
  
  
  -
  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]
  
  -
  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]
  
  
  -
  Please check that your question

RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-11 Thread Jon Hawkesworth
Title: RE: XSP page getting called TWICE! (was: Pipeline dependencies)






Probably totally irrelevant but if it stimulates thinking then maybe it will be a slight help: We had a performance problem in house once and in the course of debugging found that whenever an sql select was called, the query was run twice, once to get a count of rows and the second time to get the data. 

I'm way too new to this whole arena to see how this could be applied to xsp processing but it is as close as I've got to an idea, I'm afraid.

HTH


Jon

-Original Message-

From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]

Sent: 11 December 2001 15:37

To: [EMAIL PROTECTED]

Subject: Re: XSP page getting called TWICE! (was: Pipeline dependencies)



I posted this a couple of times here, as well as once to the Dev list. No one's written back with any suggestions so far.

I hope y'all don't mind, but I'd like to post this one more time. It's really stumping me! Please help!


==


Anyone have any thoughts on this?


What could cause an XSP page to get called twice in the same request?


Tnx!


DR



At 12:07 PM 12/7/01 -0500, you wrote:

Actually, regarding the setup below (which I mentioned in another message), I'm having a problem with it and would appreciate some help.



Take a look at the sitemap segment below. And let me clarify it a bit too:



The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is generated *dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).



This is working just fine, except for one small problem:



For some reason, on each request, this XSP page is getting executed TWICE! Although this doesn't technically cause any errors, it's pretty inefficient since it hits the database twice, generates the xsl twice, etc.



Any ideas why?



Some possible thoughts I had:



* perhaps the internal-only=true is causing this?



* perhaps an additional aspect of this setup is causing this: the cocoon:/rtf_parse generation step (not listed) is setting an attachment response header (Content-Disposition: attachment; filename=myfile.rtf) so that the file will be downloaded instead of displayed directly in the browser. Could that be causing this?



Any help appreciated!



TIA!





DR





At 11:17 AM 12/7/01 -0500, you wrote:

 It is possible. I'm using that in my site:

 

 map:pipeline

  map:match pattern=pd/mergedoc.html

  map:generate src="cocoon:/rtf_parse/

  map:transform src="cocoon:/rtf_merge_data/

  map:serialize type=rtf/

  /map:match

 /map:pipeline

 

 

 map:pipeline internal-only=true

  map:match pattern=rtf_merge_data

  map:generate type=serverpages src="pages/gen_merge_xsl.xsp/

  map:serialize type=xml/

  /map:match

 /map:pipeline

 

 

 DR



-

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]



_

This message has been checked for all known viruses by Star Internet

delivered through the MessageLabs Virus Scanning Service. For further

information visit http://www.star.net.uk/stats.asp or alternatively call

Star Internet for details on the Virus Scanning Service.





_
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit

http://www.star.net.uk/stats.asp
_
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd.
The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.



RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-11 Thread Mitchell Christensen

Have you tried modifying the code to print a stack trace with each
invocation?  This might help isolate the source of each call.

-Mitch

-Original Message-
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: XSP page getting called TWICE! (was: Pipeline dependencies)


I posted this a couple of times here, as well as once to the Dev list.  No
one's written back with any suggestions so far.

I hope y'all don't mind, but I'd like to post this one more time.  It's
really stumping me!  Please help!

==

Anyone have any thoughts on this?

What could cause an XSP page to get called twice in the same request?

Tnx!

DR


At 12:07 PM 12/7/01 -0500, you wrote:
Actually, regarding the setup below (which I mentioned in another message),
I'm having a problem with it and would appreciate some help.

Take a look at the sitemap segment below.  And let me clarify it a bit too:

The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is
generated *dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).

This is working just fine, except for one small problem:

For some reason, on each request, this XSP page is getting executed TWICE!
Although this doesn't technically cause any errors, it's pretty inefficient
since it hits the database twice, generates the xsl twice, etc.

Any ideas why?

Some possible thoughts I had:

* perhaps the internal-only=true is causing this?

* perhaps an additional aspect of this setup is causing this:  the
cocoon:/rtf_parse generation step (not listed) is setting an attachment
response header (Content-Disposition: attachment; filename=myfile.rtf) so
that the file will be downloaded instead of displayed directly in the
browser.  Could that be causing this?

Any help appreciated!

TIA!


DR


At 11:17 AM 12/7/01 -0500, you wrote:
 It is possible.  I'm using that in my site:
 
 map:pipeline
   map:match pattern=pd/mergedoc.html
   map:generate src=cocoon:/rtf_parse/
   map:transform src=cocoon:/rtf_merge_data/
   map:serialize type=rtf/
   /map:match
 /map:pipeline
 
 
 map:pipeline internal-only=true
   map:match pattern=rtf_merge_data
   map:generate type=serverpages
src=pages/gen_merge_xsl.xsp/
   map:serialize type=xml/
   /map:match
 /map:pipeline
 
 
 DR


-
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]

-
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]




RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-11 Thread David Rosenstrauch

Thanks for the suggestion.  Not sure that's the problem though.

Seems like the whole map:match pattern=rtf_merge_data pipeline is getting run 
twice.

Thanks for giving it a shot though and please let me know if you have any other 
suggestions, as I still haven't solved this.


DR


At 04:11 PM 12/11/01 +, you wrote:

Probably totally irrelevant but if it stimulates thinking then maybe it will be a 
slight help: We had a performance problem in house once and in the course of 
debugging found that whenever an sql select was called, the query was run twice, once 
to get a count of rows and the second time to get the data. 

I'm way too new to this whole arena to see how this could be applied to xsp 
processing but it is as close as I've got to an idea, I'm afraid.

HTH 

Jon 
-Original Message- 
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] 
Sent: 11 December 2001 15:37 
To: [EMAIL PROTECTED] 
Subject: Re: XSP page getting called TWICE! (was: Pipeline dependencies) 

I posted this a couple of times here, as well as once to the Dev list.  No one's 
written back with any suggestions so far.

I hope y'all don't mind, but I'd like to post this one more time.  It's really 
stumping me!  Please help! 

== 

Anyone have any thoughts on this? 

What could cause an XSP page to get called twice in the same request? 

Tnx! 

DR 

At 12:07 PM 12/7/01 -0500, you wrote: 
 Actually, regarding the setup below (which I mentioned in another message), I'm 
having a problem with it and would appreciate some help.

  
 Take a look at the sitemap segment below.  And let me clarify it a bit too: 
  
 The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is 
generated *dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).

  
 This is working just fine, except for one small problem: 
  
 For some reason, on each request, this XSP page is getting executed TWICE!  
Although this doesn't technically cause any errors, it's pretty inefficient since it 
hits the database twice, generates the xsl twice, etc.

  
 Any ideas why? 
  
 Some possible thoughts I had: 
  
 * perhaps the internal-only=true is causing this? 
  
 * perhaps an additional aspect of this setup is causing this:  the 
cocoon:/rtf_parse generation step (not listed) is setting an attachment response 
header (Content-Disposition: attachment; filename=myfile.rtf) so that the file will 
be downloaded instead of displayed directly in the browser.  Could that be causing 
this?

  
 Any help appreciated! 
  
 TIA! 
  
  
 DR 
  
  
 At 11:17 AM 12/7/01 -0500, you wrote: 
  It is possible.  I'm using that in my site: 
   
  map:pipeline 
map:match pattern=pd/mergedoc.html 
map:generate src=cocoon:/rtf_parse/ 
map:transform src=cocoon:/rtf_merge_data/ 
map:serialize type=rtf/ 
/map:match 
  /map:pipeline 
   
   
  map:pipeline internal-only=true 
map:match pattern=rtf_merge_data 
map:generate type=serverpages 
src=pages/gen_merge_xsl.xsp/ 
map:serialize type=xml/ 
/map:match 
  /map:pipeline 
   
   
  DR 

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

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

_ 
This message has been checked for all known viruses by Star Internet 
delivered through the MessageLabs Virus Scanning Service. For further 
information visit http://www.star.net.uk/stats.asphttp://www.star.net.uk/stats.asp 
or alternatively call 
Star Internet for details on the Virus Scanning Service. 

_
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asphttp://www.star.net.uk/stats.asp
_
Any views or personal opinions expressed within this email may not be those of Talis 
Information Ltd.
The content of this email message and any files that may be attached are 
confidential, and for the usage of the intended recipient only. If you are not the 
intended recipient, then please return this message to the sender and delete it. Any 
use of this e-mail by an unauthorised recipient is prohibited.


-
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

RE: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-11 Thread David Rosenstrauch

I did.  From the trace, it seems like the whole map:match pattern=rtf_merge_data 
pipeline is getting run twice - which I found even more confusing.

Not sure why it should need to run that pipeline twice.  Clearly that's happening 
because of some combination of:  a) it's an internal pipeline, b) I'm using the 
results of that pipeline in a transform in another pipeline.

I can't figure out for the life of me why it should be run twice though.

Thanks for giving it a shot though and please let me know if you have any other 
suggestions, as I still haven't solved this.


DR





At 08:58 AM 12/11/01 -0800, you wrote:
Have you tried modifying the code to print a stack trace with each
invocation?  This might help isolate the source of each call.

-Mitch

-Original Message-
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: XSP page getting called TWICE! (was: Pipeline dependencies)


I posted this a couple of times here, as well as once to the Dev list.  No
one's written back with any suggestions so far.

I hope y'all don't mind, but I'd like to post this one more time.  It's
really stumping me!  Please help!

==

Anyone have any thoughts on this?

What could cause an XSP page to get called twice in the same request?

Tnx!

DR


At 12:07 PM 12/7/01 -0500, you wrote:
 Actually, regarding the setup below (which I mentioned in another message),
I'm having a problem with it and would appreciate some help.
 
 Take a look at the sitemap segment below.  And let me clarify it a bit too:
 
 The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is
generated *dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).
 
 This is working just fine, except for one small problem:
 
 For some reason, on each request, this XSP page is getting executed TWICE!
Although this doesn't technically cause any errors, it's pretty inefficient
since it hits the database twice, generates the xsl twice, etc.
 
 Any ideas why?
 
 Some possible thoughts I had:
 
 * perhaps the internal-only=true is causing this?
 
 * perhaps an additional aspect of this setup is causing this:  the
cocoon:/rtf_parse generation step (not listed) is setting an attachment
response header (Content-Disposition: attachment; filename=myfile.rtf) so
that the file will be downloaded instead of displayed directly in the
browser.  Could that be causing this?
 
 Any help appreciated!
 
 TIA!
 
 
 DR
 
 
 At 11:17 AM 12/7/01 -0500, you wrote:
  It is possible.  I'm using that in my site:
  
  map:pipeline
map:match pattern=pd/mergedoc.html
map:generate src=cocoon:/rtf_parse/
map:transform src=cocoon:/rtf_merge_data/
map:serialize type=rtf/
/map:match
  /map:pipeline
  
  
  map:pipeline internal-only=true
map:match pattern=rtf_merge_data
map:generate type=serverpages
src=pages/gen_merge_xsl.xsp/
map:serialize type=xml/
/map:match
  /map:pipeline
  
  
  DR


-
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]

-
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] 


-
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]




Re: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-10 Thread David Rosenstrauch

Anyone have any thoughts on this?

What could cause an XSP page to get called twice in the same request?

Tnx!

DR


At 12:07 PM 12/7/01 -0500, you wrote:
Actually, regarding the setup below (which I mentioned in another message), I'm 
having a problem with it and would appreciate some help.

Take a look at the sitemap segment below.  And let me clarify it a bit too:

The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is generated 
*dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).

This is working just fine, except for one small problem:

For some reason, on each request, this XSP page is getting executed TWICE!  Although 
this doesn't technically cause any errors, it's pretty inefficient since it hits the 
database twice, generates the xsl twice, etc.

Any ideas why?

Some possible thoughts I had:

* perhaps the internal-only=true is causing this?

* perhaps an additional aspect of this setup is causing this:  the 
cocoon:/rtf_parse generation step (not listed) is setting an attachment response 
header (Content-Disposition: attachment; filename=myfile.rtf) so that the file will 
be downloaded instead of displayed directly in the browser.  Could that be causing 
this?

Any help appreciated!

TIA!


DR


At 11:17 AM 12/7/01 -0500, you wrote:
 It is possible.  I'm using that in my site:
 
 map:pipeline
   map:match pattern=pd/mergedoc.html
   map:generate src=cocoon:/rtf_parse/
   map:transform src=cocoon:/rtf_merge_data/
   map:serialize type=rtf/
   /map:match
 /map:pipeline
 
 
 map:pipeline internal-only=true
   map:match pattern=rtf_merge_data
   map:generate type=serverpages src=pages/gen_merge_xsl.xsp/
   map:serialize type=xml/
   /map:match
 /map:pipeline
 
 
 DR


-
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] 


-
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]




Pipeline dependencies

2001-12-07 Thread Nick Entin

Hello!

Does anybody know is that possible to make one pipeline to be dependent
on another?
Like I have a 2 frames in result - left frame is processed by one
pipeline and right - by another.
I want to be sure that the 'left' pipeline is executed first, because it
produces some data, used by the 'right' one.

Another possible solution for me would be if a transformer could get as
src result of a pipeline, like:

  map:match pattern=TRANSFORMER
 map:generate src=data/test.xml /
 map:transform src=data/markedxsl.xsl /
 map:serialize type=xml /
  /map:match

  map:match pattern=xxx
 map:generate src=data/test.xml /
 map:transform src=TRANSFORMER /
 map:serialize type=html /
  /map:match

My attempts to make it running failed. Do I need additional things
configured?

Thanks!

Best wishes,
Nick


-
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]




Re: Pipeline dependencies

2001-12-07 Thread Nicola Ken Barozzi


- Original Message -
From: Nick Entin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 07, 2001 12:02 PM
Subject: Pipeline dependencies


 Hello!

 Does anybody know is that possible to make one pipeline to be dependent
 on another?
 Like I have a 2 frames in result - left frame is processed by one
 pipeline and right - by another.
 I want to be sure that the 'left' pipeline is executed first, because it
 produces some data, used by the 'right' one.

 Another possible solution for me would be if a transformer could get as
 src result of a pipeline, like:

   map:match pattern=TRANSFORMER
  map:generate src=data/test.xml /
  map:transform src=data/markedxsl.xsl /
  map:serialize type=xml /
   /map:match

   map:match pattern=xxx
  map:generate src=data/test.xml /
  map:transform src=TRANSFORMER /
  map:serialize type=html /
   /map:match

 My attempts to make it running failed. Do I need additional things
 configured?


AFAIK, this is not possible.
Having the same problem, I did another thing; invoked only the first page
and put a script
at the end of it that loads the other document in the other frame.

Nicola Ken Barozzi These are the days of miracle and wonder...
...so don't cry baby, don't cry
[EMAIL PROTECTED] Paul Simon


-
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]




Re: Pipeline dependencies

2001-12-07 Thread David Rosenstrauch

It is possible.  I'm using that in my site:

map:pipeline
 map:match pattern=pd/mergedoc.html
 map:generate src=_thesource_/
 map:transform src=cocoon:/rtf_merge_data/
 map:serialize type=html/
 /map:match
/map:pipeline


map:pipeline internal-only=true
 map:match pattern=rtf_merge_data
 map:generate type=serverpages src=pages/gen_merge_xsl.xsp/
 map:serialize type=xml/
 /map:match
/map:pipeline


DR



At 12:22 PM 12/7/01 +0100, you wrote:

- Original Message -
From: Nick Entin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 07, 2001 12:02 PM
Subject: Pipeline dependencies


  Hello!
 
  Does anybody know is that possible to make one pipeline to be dependent
  on another?
  Like I have a 2 frames in result - left frame is processed by one
  pipeline and right - by another.
  I want to be sure that the 'left' pipeline is executed first, because it
  produces some data, used by the 'right' one.
 
  Another possible solution for me would be if a transformer could get as
  src result of a pipeline, like:
 
map:match pattern=TRANSFORMER
   map:generate src=data/test.xml /
   map:transform src=data/markedxsl.xsl /
   map:serialize type=xml /
/map:match
 
map:match pattern=xxx
   map:generate src=data/test.xml /
   map:transform src=TRANSFORMER /
   map:serialize type=html /
/map:match
 
  My attempts to make it running failed. Do I need additional things
  configured?


AFAIK, this is not possible.
Having the same problem, I did another thing; invoked only the first page
and put a script
at the end of it that loads the other document in the other frame.

Nicola Ken Barozzi These are the days of miracle and wonder...
...so don't cry baby, don't cry
[EMAIL PROTECTED] Paul Simon


-
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] 


-
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]




XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-07 Thread David Rosenstrauch

Actually, regarding the setup below (which I mentioned in another message), I'm having 
a problem with it and would appreciate some help.

Take a look at the sitemap segment below.  And let me clarify it a bit too:

The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is generated 
*dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).

This is working just fine, except for one small problem:

For some reason, on each request, this XSP page is getting executed TWICE!  Although 
this doesn't technically cause any errors, it's pretty inefficient since it hits the 
database twice, generates the xsl twice, etc.

Any ideas why?

Some possible thoughts I had:

* perhaps the internal-only=true is causing this?

* perhaps an additional aspect of this setup is causing this:  the cocoon:/rtf_parse 
generation step (not listed) is setting an attachment response header 
(Content-Disposition: attachment; filename=myfile.rtf) so that the file will be 
downloaded instead of displayed directly in the browser.  Could that be causing this?

Any help appreciated!

TIA!


DR


At 11:17 AM 12/7/01 -0500, you wrote:
It is possible.  I'm using that in my site:

map:pipeline
  map:match pattern=pd/mergedoc.html
  map:generate src=cocoon:/rtf_parse/
  map:transform src=cocoon:/rtf_merge_data/
  map:serialize type=rtf/
  /map:match
/map:pipeline


map:pipeline internal-only=true
  map:match pattern=rtf_merge_data
  map:generate type=serverpages src=pages/gen_merge_xsl.xsp/
  map:serialize type=xml/
  /map:match
/map:pipeline


DR


-
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]




Re: XSP page getting called TWICE! (was: Pipeline dependencies)

2001-12-07 Thread David Rosenstrauch

Anyone have any thoughts on this?

What could cause an XSP page to get called twice in the same request?

Tnx!

DR


At 12:07 PM 12/7/01 -0500, you wrote:
Actually, regarding the setup below (which I mentioned in another message), I'm 
having a problem with it and would appreciate some help.

Take a look at the sitemap segment below.  And let me clarify it a bit too:

The XSL stylesheet that I'm using in the transform on pd/mergedoc.html is generated 
*dynamically*, from an xsp page (pages/gen_merge_xsl.xsp).

This is working just fine, except for one small problem:

For some reason, on each request, this XSP page is getting executed TWICE!  Although 
this doesn't technically cause any errors, it's pretty inefficient since it hits the 
database twice, generates the xsl twice, etc.

Any ideas why?

Some possible thoughts I had:

* perhaps the internal-only=true is causing this?

* perhaps an additional aspect of this setup is causing this:  the 
cocoon:/rtf_parse generation step (not listed) is setting an attachment response 
header (Content-Disposition: attachment; filename=myfile.rtf) so that the file will 
be downloaded instead of displayed directly in the browser.  Could that be causing 
this?

Any help appreciated!

TIA!


DR


At 11:17 AM 12/7/01 -0500, you wrote:
 It is possible.  I'm using that in my site:
 
 map:pipeline
   map:match pattern=pd/mergedoc.html
   map:generate src=cocoon:/rtf_parse/
   map:transform src=cocoon:/rtf_merge_data/
   map:serialize type=rtf/
   /map:match
 /map:pipeline
 
 
 map:pipeline internal-only=true
   map:match pattern=rtf_merge_data
   map:generate type=serverpages src=pages/gen_merge_xsl.xsp/
   map:serialize type=xml/
   /map:match
 /map:pipeline
 
 
 DR


-
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] 


-
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]