building cocoon fails (The requested operation cannot be performed on a file with a user-mapped section open)

2008-07-11 Thread Robby Pelssers
Hi list, Anyone who encountered a similar problem? And does anybody have an idea how to fix this problem? Below are 2 build trials and it does not always fail at the same spot. I already googled on the error The requested operation cannot be performed on a file with a user-mapped section

RE: building cocoon fails (The requested operation cannot be performed on a file with a user-mapped section open)

2008-07-11 Thread Robby Pelssers
I ran mvn with the -e switch and this time it builded ok Maybe it went well because it took a little longer with debugging turned on so the chance of a file getting locked twice was dramatically reduced. And just in case you are wondering where maven comes in to the picture: plugin

Re: CSVGenerator separators

2008-07-11 Thread Andy Stevens
2008/7/9 netBrackets [EMAIL PROTECTED]: Is there any way to tell the CSVGenerator to use one or more contiguous spaces as a seperator? You can tell it to use a single space: map:match pattern=importSSV/* map:generate type=csv src=inputs/{1} map:parameter

Re: Help with tree widget

2008-07-11 Thread Ralph Rauscher
Hi Peter, see below for a sample on how it works in 2.1.11 - might work as well on 2.2 or at least give you some pointers. model: ?xml version=1.0? fd:form xmlns:fd=http://apache.org/cocoon/forms/1.0#definition; fd:widgets !-- fd:tree id=myTree fd:tree-model type=java

Get the URL of the originating client into XSLT

2008-07-11 Thread Kjetil Kjernsmo
Hi all, I've been trying to figure out how to get the URL of the originating client, i.e. the URL that the end user has in his address bar when he gets the response. I want to have access to this URL in my XSLT, preferably through a param variable. I've been experimenting a bit, but I cannot

Re: Get the URL of the originating client into XSLT

2008-07-11 Thread Jeroen Reijn
Kjetil, have you tried using the request input module in your sitemap? You should be able to get it with {request:serverName} or something similar. Regards, Jeroen Kjetil Kjernsmo wrote: Hi all, I've been trying to figure out how to get the URL of the originating client, i.e. the URL that

Can't match elements with colons

2008-07-11 Thread Jeff Schmitz
Hello, I'm trying to take the output of the CSVGenerator and transform it. However, my xslt will not match any of the elements that have colons in them. e.g. for the following xml generated by CSVGenerator: ?xml version=1.0 encoding=ISO-8859-1?relex

Re: CSVGenerator separators

2008-07-11 Thread Jeff Schmitz
I'll give it a try as soon as I can figure out how to match element names that have a colon in them. As it is, the following will never match anything: xsl:template match=csv:field On Jul 11, 2008, at 7:30 AM, Andy Stevens wrote: 2008/7/9 netBrackets [EMAIL PROTECTED]: Is there any

Re: Can't match elements with colons

2008-07-11 Thread solprovider
On 7/11/08, Jeff Schmitz [EMAIL PROTECTED] wrote: Hello, I'm trying to take the output of the CSVGenerator and transform it. However, my xslt will not match any of the elements that have colons in them. e.g. for the following xml generated by CSVGenerator: ?xml version=1.0

Re: Can't match elements with colons

2008-07-11 Thread Jeff Schmitz
OK, figured it out. It was because of the '#' at the end of the csv namespace declaration in my xslt stylesheet. This is a very common thing to do when using owl namespaces, however apparently xslt doesn't like it, I guess because it doesn't match exactly the csv namespace declaration in

Re: CSVGenerator separators

2008-07-11 Thread solprovider
On 7/9/08, netBrackets [EMAIL PROTECTED] wrote: Is there any way to tell the CSVGenerator to use one or more contiguous spaces as a seperator? You can tell it to use a single space: map:match pattern=importSSV/* map:generate type=csv src=inputs/{1} map:parameter

Re: Can't match elements with colons

2008-07-11 Thread solprovider
On 7/11/08, Jeff Schmitz [EMAIL PROTECTED] wrote: OK, figured it out. It was because of the '#' at the end of the csv namespace declaration in my xslt stylesheet. This is a very common thing to do when using owl namespaces, however apparently xslt doesn't like it, I guess because it doesn't

Re: call pipeline from XSLT

2008-07-11 Thread solprovider
On 7/10/08, Heather Rankin [EMAIL PROTECTED] wrote: I want to be able to call a pipeline from another pipeline's XSLT in the same sitemap. (The reason I need to call the pipeline from the XSLT as opposed to from the sitemap directly is because I need to pass the XML input data as