Re: internal pipeline
Ali Mesbah wrote: [...] You can try to set the log level to DEBUG and look at the sitemap log to see if the correct steps are executed. No. There is a major difference between the log information when the "xms/test" pipeline is called directly and when it is called by the second pipeline through the Cocoon: protocol. I even added a LOG Transformer after the first pipeline; when using Cocoon: protocol, this log file remains empty: ([setup] [Thu Jun 05 11:59:01 CEST 2003] --) while when called directly it is filled by all the right steps. This is strange ... The next debugging step could be to save the output of your first pipeline as an XSLT file and to use this directly without the cocoon: protocol. Did that too. And indeed when I save the output of the first pipeline and use it as a normal source for the second (view) pipeline it goes as wished. So I think my assumption was correct that it has to do with the use of the Cocoon: protocol as the src of a transformer. Have you ever by the way used it in this way too (Cocoon: as the src of XSLT (not XSP) via pipelines)? Yes, what I meant is that I used an XSP to generate XSLT that was used in a transformation step, e.g., somethink like: This worked perfectly, at least with Cocoon 2.1 M1 (I used it to prototype a transformer). Sorry I can't help you, the only thing I could suggest is to try it with 2.1-M1 or later if you're using 2.0.?. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: internal pipeline
Andreas, As quoted from Andreas Hartmann <[EMAIL PROTECTED]>: > Hi Ali, > > Ali Mesbah wrote: > > >Hi all, > >I have a problem and don't know if it is a bug in Cocoon or if I'm doing > >something wrong. > > > >What I have is a pipeline which transforms an XML (source) file into an > >XSLT > >(target) stylesheet: > > > > > > > > > > > > > > > > > >now I'd like to use the output as the source of another pipeline: > > > > > > > > > > > > > > > > > >I don't get any errors but the HTML output of the "view" pipeline is not > >the > >expected (I have checked the output of the first pipeline and that is > >correct. I > >assume it has something to do with the way I use "cocoon:/..." as the > >source of > >the second transformer). Any ideas? > > Your pipelines look OK (if I didn't miss anything). You're using > the cocoon: protocol correctly. I also tried this kind of "stylesheet > generation" (using XSP) and it worked very well. So I guess your > problem is somewhere in the last transformation step. > > You can try to set the log level to DEBUG and look at the sitemap > log to see if the correct steps are executed. No. There is a major difference between the log information when the "xms/test" pipeline is called directly and when it is called by the second pipeline through the Cocoon: protocol. I even added a LOG Transformer after the first pipeline; when using Cocoon: protocol, this log file remains empty: ([setup] [Thu Jun 05 11:59:01 CEST 2003] --) while when called directly it is filled by all the right steps. > The next debugging step could be to save the output of your first > pipeline as an XSLT file and to use this directly without the > cocoon: protocol. Did that too. And indeed when I save the output of the first pipeline and use it as a normal source for the second (view) pipeline it goes as wished. So I think my assumption was correct that it has to do with the use of the Cocoon: protocol as the src of a transformer. Have you ever by the way used it in this way too (Cocoon: as the src of XSLT (not XSP) via pipelines)? > HTH, > Andreas -- -- 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: internal pipeline
Hi Ali, Ali Mesbah wrote: Hi all, I have a problem and don't know if it is a bug in Cocoon or if I'm doing something wrong. What I have is a pipeline which transforms an XML (source) file into an XSLT (target) stylesheet: now I'd like to use the output as the source of another pipeline: I don't get any errors but the HTML output of the "view" pipeline is not the expected (I have checked the output of the first pipeline and that is correct. I assume it has something to do with the way I use "cocoon:/..." as the source of the second transformer). Any ideas? Your pipelines look OK (if I didn't miss anything). You're using the cocoon: protocol correctly. I also tried this kind of "stylesheet generation" (using XSP) and it worked very well. So I guess your problem is somewhere in the last transformation step. You can try to set the log level to DEBUG and look at the sitemap log to see if the correct steps are executed. The next debugging step could be to save the output of your first pipeline as an XSLT file and to use this directly without the cocoon: protocol. HTH, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
internal pipeline
Hi all, I have a problem and don't know if it is a bug in Cocoon or if I'm doing something wrong. What I have is a pipeline which transforms an XML (source) file into an XSLT (target) stylesheet: now I'd like to use the output as the source of another pipeline: I don't get any errors but the HTML output of the "view" pipeline is not the expected (I have checked the output of the first pipeline and that is correct. I assume it has something to do with the way I use "cocoon:/..." as the source of the second transformer). Any ideas? Thanks, -- -- 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: pass parameters to internal pipeline
Thanks. Both Alfred and Marco's suggestion worked. Although it's not as elegant as I'd like, at least I know it can do what I want. Placing the parameters into the request allowed me to bypass the fact that generators don't take parameters I-Lin Kuo, Ann Arbor, MI Original Message Follows From: "Nathaniel Alfred" <[EMAIL PROTECTED]> Try this: HTH, Alfred. -Original Message- From: I-Lin Kuo [mailto:[EMAIL PROTECTED] Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following pipeline: I-Lin Kuo, Ann Arbor, MI _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: pass parameters to internal pipeline
Try this: HTH, Alfred. -Original Message- From: I-Lin Kuo [mailto:[EMAIL PROTECTED] Sent: Sonntag, 2. März 2003 13:18 To: [EMAIL PROTECTED] Subject: pass parameters to internal pipeline Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following pipeline: I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pass parameters to internal pipeline
Unfortunately, as long as you are using the cocoon:// protocol, you are going to run into the same problem with passing parameters to the pipeline. Both generators use the resolver to retrieve a SitemapSource, which will place any parameters you pass to it into the objectModel. I think Marco's suggestion of using request parameters is the best way to go. Brian On Sunday, March 2, 2003, at 08:26 AM, I-Lin Kuo wrote: The FileGenerator doesn't use any parameters. Maybe the problem is that I'm passing to a FileGenerator. I'm going to try passing to an xsp instead... _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus - 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: pass parameters to internal pipeline
The FileGenerator doesn't use any parameters. Maybe the problem is that I'm passing to a FileGenerator. I'm going to try passing to an xsp instead... _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: pass parameters to internal pipeline
although it's a bit clumsy, you *can* use request parameters with an internal pipeline; you tell the xslt transformer to use request parameters and should then be able to access these from within your stylesheet. > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Auftrag von I-Lin Kuo > Gesendet: Sonntag, 2. März 2003 13:18 > An: [EMAIL PROTECTED] > Betreff: pass parameters to internal pipeline > > > Is it possible to pass parameters to an internal pipeline? > > This doesn't work for me: > > > > > > > > > > > > > > P.S. Just to be sure that I haven't made any dumb mistakes, I've checked > that I have a top-level xsl:param in my style sheet getParam.xsl > which picks > up the parameter from the following pipeline: > > > > > > > > > > I-Lin Kuo, Ann Arbor, MI > Macromedia Certified ColdFusion 5.0 Advanced Developer > Sun Certified Java 2 Programmer > Ann Arbor Java Users Group (http://www.aajug.org) > > > _ > The new MSN 8: smart spam protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > - > 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: pass parameters to internal pipeline
Upon a little closer examination, it appears that passing parameters to the source resolver will only make them available in the objectModel of the sitemap you are calling. I don't know if that will help you or not. Outside of that, it doesn't appear that there is any other mechanism to pass information to a sitemap source that I can see... Brian On Sunday, March 2, 2003, at 07:46 AM, Brian Johnson wrote: Ok, I see what you are trying to do... Again though, the FileGenerator doesn't use any parameters that are passed to it. It is possible to extend FileGenerator and override the setup method to pass parameters to the source resolver. I believe this would provide the functionality you are looking for. Brian On Sunday, March 2, 2003, at 07:29 AM, Brian Johnson wrote: What do you want to do with this parameter? The FileGenerator doesn't use any parameters. The TraxTransformer allows you to pass parameters to the stylesheet that can be accessed with xsl:param, but there is no similar function for a generic xml document. The FileGenerator simply loads the xml document and creates SAX events from it. Brian On Sunday, March 2, 2003, at 07:17 AM, I-Lin Kuo wrote: Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following >> pipeline: I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - 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] - 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: pass parameters to internal pipeline
What do you want to do with this parameter? The FileGenerator doesn't use any parameters. The TraxTransformer allows you to pass parameters to the stylesheet that can be accessed with xsl:param, but there is no similar function for a generic xml document. I've got my first Cocoon app up and running, but it's structured very poorly and I'm exploring reuse possibilities of Cocoon. There's a search engine part of my code which generates the SQL to the database that I'd like to reuse. I'd like to process request parameters differently based on which part of the site the user comes from, and then pass the processed parameters to my search engine component. I can do this using a selector of course, but that requires me to duplicate code in each branch of the selector, and exposes the internal pipeline of the search engine. I'd like to keep the search engine related pipeline all in one place to keep changes synchronized. It also makes it easier for me to hand this off to someone else and say "to use the search engine, all you have to do is pass these parameters to cocoon:searchengine.xml" I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pass parameters to internal pipeline
Ok, I see what you are trying to do... Again though, the FileGenerator doesn't use any parameters that are passed to it. It is possible to extend FileGenerator and override the setup method to pass parameters to the source resolver. I believe this would provide the functionality you are looking for. Brian On Sunday, March 2, 2003, at 07:29 AM, Brian Johnson wrote: What do you want to do with this parameter? The FileGenerator doesn't use any parameters. The TraxTransformer allows you to pass parameters to the stylesheet that can be accessed with xsl:param, but there is no similar function for a generic xml document. The FileGenerator simply loads the xml document and creates SAX events from it. Brian On Sunday, March 2, 2003, at 07:17 AM, I-Lin Kuo wrote: Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following >> pipeline: I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pass parameters to internal pipeline
What do you want to do with this parameter? The FileGenerator doesn't use any parameters. The TraxTransformer allows you to pass parameters to the stylesheet that can be accessed with xsl:param, but there is no similar function for a generic xml document. The FileGenerator simply loads the xml document and creates SAX events from it. Brian On Sunday, March 2, 2003, at 07:17 AM, I-Lin Kuo wrote: Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following pipeline: I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - 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]
pass parameters to internal pipeline
Is it possible to pass parameters to an internal pipeline? This doesn't work for me: P.S. Just to be sure that I haven't made any dumb mistakes, I've checked that I have a top-level xsl:param in my style sheet getParam.xsl which picks up the parameter from the following pipeline: I-Lin Kuo, Ann Arbor, MI Macromedia Certified ColdFusion 5.0 Advanced Developer Sun Certified Java 2 Programmer Ann Arbor Java Users Group (http://www.aajug.org) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Internal Pipeline - external access
Silke Schön wrote: >Hello! > >In the pipelines part of my sitemap.xmap I created a second, internal pipeline for a >pdf-document. The sheet works fine- but as well internal as EXTERNAL- what I wanted >to avoid. > I don't get this. >I can't find the problem. >What went wrong? > What's the problem? >Where can I modify the settings for what exactly should be treated as external and >what as internal (internal for instance just the localhost)? > "Internal" pipeline means: only Cocoon itself can access this pipeline. Nobody outside Cocoon, even from localhost, can access this pipeline. If you want to decide what to serve based on host, use host matchers and selectors. >Should I use the "cocoon:/int" even if I removed the "/cocoon" from my usual URI (I >guess that really doesn't matter - anyway)? > In "cocoon:/int", "cocoon:" part is *protocol*. See docs. See samples under cocoon/sub/ as well. Vadim >Well, here are my pipelines: > ># ># ># ># ># ># ># ># ># ># ># ># # ># ># ># > >I'd be very pleased to get some help, as I am quite new to cocoon. And a bit >desperate as well. >Thank you > >Silke > > - 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]>
Internal Pipeline - external access
Hello! In the pipelines part of my sitemap.xmap I created a second, internal pipeline for a pdf-document. The sheet works fine- but as well internal as EXTERNAL- what I wanted to avoid. I can't find the problem. What went wrong? Where can I modify the settings for what exactly should be treated as external and what as internal (internal for instance just the localhost)? Should I use the "cocoon:/int" even if I removed the "/cocoon" from my usual URI (I guess that really doesn't matter - anyway)? Well, here are my pipelines: # # # # # # # # # # # ... # ... # # # # # ... # ... # # I'd be very pleased to get some help, as I am quite new to cocoon. And a bit desperate as well. Thank you Silke __ Den Komfort von WEB.DE FreeMail nutzen, aber die alten E-Mail-Adressen nicht aufgeben? Kein Problem: http://freemail.web.de/?mc=021128 - 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]>
