Re: Generate XSL with XSP?
Sorry for accidentally sending private mail to the list. My fault. Won't happen again. Robert Du hast es hingekriegt ?!!! Yipee! Ich habs genahnt das das geht. Super, danke Thommi, must mir heute abend mal zeigen was bei mir falsch war. Dann kannste ja mindestens 4 XSL wegschmeissen Und dann gibts auch nur noch basepath und net mehr cms. Col Rob - Original Message - From: Thomas Haditsch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 3:22 AM Subject: Re: Generate XSL with XSP? sorry, should have used 'cocoon:/' instead of 'cocoon://'. that solved the problem! At 03:19 04.03.2003 +0100, you wrote: no, that's not the problem. i managed to dynamically create the xsl using a custom generator instead of a xsp, but now the xsl that includes it complains that the variable 'basepath' has not been defined if i do it this way: xsl:include href=cocoon://include-basepath.xsl/ and if i do xsl:include href=include-basepath.xsl/ it tries to load the file from disk. any ideas if (and how) this can be solved? thanx in advance, thomas At 00:47 04.03.2003 +0100, you wrote: Thanks alot for your answer. Yes that was wrong BUT I didn't even came to the point where including the stylesheet was of interest. That is because the XSP did never generate the desired XSL. The output of my XSP was just an emtpty ?xml ... Tag. No other elements were created. I guess it a namespace problem. What do you think? Robert - Original Message - From: Upayavira [EMAIL PROTECTED] To: Robert Sösemann [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, March 03, 2003 8:03 PM Subject: Re: Generate XSL with XSP? Robert, xsl:include href=include-basepath.xsl/ Is it as simple as changing this line to: xsl:include href=cocoon:/include-basepath.xsl/ to allow the include to call an internal pipeline? Regards, Upayavira - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generate XSL with XSP?
Robert, xsl:include href=include-basepath.xsl/ Is it as simple as changing this line to: xsl:include href=cocoon:/include-basepath.xsl/ to allow the include to call an internal pipeline? Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generate XSL with XSP?
no, that's not the problem. i managed to dynamically create the xsl using a custom generator instead of a xsp, but now the xsl that includes it complains that the variable 'basepath' has not been defined if i do it this way: xsl:include href=cocoon://include-basepath.xsl/ and if i do xsl:include href=include-basepath.xsl/ it tries to load the file from disk. any ideas if (and how) this can be solved? thanx in advance, thomas At 00:47 04.03.2003 +0100, you wrote: Thanks alot for your answer. Yes that was wrong BUT I didn't even came to the point where including the stylesheet was of interest. That is because the XSP did never generate the desired XSL. The output of my XSP was just an emtpty ?xml ... Tag. No other elements were created. I guess it a namespace problem. What do you think? Robert - Original Message - From: Upayavira [EMAIL PROTECTED] To: Robert Sösemann [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, March 03, 2003 8:03 PM Subject: Re: Generate XSL with XSP? Robert, xsl:include href=include-basepath.xsl/ Is it as simple as changing this line to: xsl:include href=cocoon:/include-basepath.xsl/ to allow the include to call an internal pipeline? Regards, Upayavira - 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: Generate XSL with XSP?
sorry, should have used 'cocoon:/' instead of 'cocoon://'. that solved the problem! At 03:19 04.03.2003 +0100, you wrote: no, that's not the problem. i managed to dynamically create the xsl using a custom generator instead of a xsp, but now the xsl that includes it complains that the variable 'basepath' has not been defined if i do it this way: xsl:include href=cocoon://include-basepath.xsl/ and if i do xsl:include href=include-basepath.xsl/ it tries to load the file from disk. any ideas if (and how) this can be solved? thanx in advance, thomas At 00:47 04.03.2003 +0100, you wrote: Thanks alot for your answer. Yes that was wrong BUT I didn't even came to the point where including the stylesheet was of interest. That is because the XSP did never generate the desired XSL. The output of my XSP was just an emtpty ?xml ... Tag. No other elements were created. I guess it a namespace problem. What do you think? Robert - Original Message - From: Upayavira [EMAIL PROTECTED] To: Robert Sösemann [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, March 03, 2003 8:03 PM Subject: Re: Generate XSL with XSP? Robert, xsl:include href=include-basepath.xsl/ Is it as simple as changing this line to: xsl:include href=cocoon:/include-basepath.xsl/ to allow the include to call an internal pipeline? Regards, Upayavira - 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: Generate XSL with XSP?
Du hast es hingekriegt ?!!! Yipee! Ich habs genahnt das das geht. Super, danke Thommi, must mir heute abend mal zeigen was bei mir falsch war. Dann kannste ja mindestens 4 XSL wegschmeissen Und dann gibts auch nur noch basepath und net mehr cms. Col Rob - Original Message - From: Thomas Haditsch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 3:22 AM Subject: Re: Generate XSL with XSP? sorry, should have used 'cocoon:/' instead of 'cocoon://'. that solved the problem! At 03:19 04.03.2003 +0100, you wrote: no, that's not the problem. i managed to dynamically create the xsl using a custom generator instead of a xsp, but now the xsl that includes it complains that the variable 'basepath' has not been defined if i do it this way: xsl:include href=cocoon://include-basepath.xsl/ and if i do xsl:include href=include-basepath.xsl/ it tries to load the file from disk. any ideas if (and how) this can be solved? thanx in advance, thomas At 00:47 04.03.2003 +0100, you wrote: Thanks alot for your answer. Yes that was wrong BUT I didn't even came to the point where including the stylesheet was of interest. That is because the XSP did never generate the desired XSL. The output of my XSP was just an emtpty ?xml ... Tag. No other elements were created. I guess it a namespace problem. What do you think? Robert - Original Message - From: Upayavira [EMAIL PROTECTED] To: Robert Sösemann [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, March 03, 2003 8:03 PM Subject: Re: Generate XSL with XSP? Robert, xsl:include href=include-basepath.xsl/ Is it as simple as changing this line to: xsl:include href=cocoon:/include-basepath.xsl/ to allow the include to call an internal pipeline? Regards, Upayavira - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
