Re: Custom DOM transformer

2007-11-20 Thread Jean-Claude Vogel
Hello, Thanks a lot for your answers which helped me to understand my problem. It was finally not a Cocoon usage problem like I believed too long, I had a releaseConnection on my PostMethod before logging the resulting body on the client side. So the http response body was ever null. In fact,

Re: Custom DOM transformer

2007-11-19 Thread Jean-Claude Vogel
Thank you, effectively it was just a mistake during my drag and drop to write my email. The true code is : map:pipeline map:match pattern=tentative map:generate type=stream map:parameter name=defaultContentType value=text/xml/

Re: Custom DOM transformer

2007-11-19 Thread solprovider
You have proven the problem is not in the custom DOMTransformer. Warrell suggests using the Request Generator. I generate form data using the Server Pages Generator with an XSP. I wrote this when I was very new to Cocoon. It works, but I would be very interested in a debate about the best

Custom DOM transformer

2007-11-16 Thread Jean-Claude Vogel
Hello guys, I would like to write my own dom transformer. So I simply wrote the following in order to get firstly an identity transformer : public class TestTransformer extends AbstractDOMTransformer { private Request request; public void setup(SourceResolver resolver, Map

Re: Custom DOM transformer

2007-11-16 Thread solprovider
Remove the map:transform type=testTransformer / line to verify the problem is in the transformer. Make certain everything worked without the transformer, then add the line and see if the problem recurs. solprovider On 11/16/07, Jean-Claude Vogel [EMAIL PROTECTED] wrote: Here is the concerned

Re: Custom DOM transformer

2007-11-16 Thread Jean-Claude Vogel
Here is the concerned extract of my sitemap : map:pipeline map:generate type=stream map:parameter name=defaultContentType value=text/xml/ /map:generate map:match pattern=tentative map:transform type=testTransformer /

Re: Custom DOM transformer

2007-11-16 Thread warrell harries
Surely some mistake (probably a typo) but your pipeline should be :- map:pipeline map:match pattern=tentative map:generate type=stream map:parameter name=defaultContentType value=text/xml/ /map:generate map:transform type=testTransformer / map:serialize type=xml/ /map:match

Re: Custom DOM transformer

2007-11-16 Thread warrell harries
Hi Jean-Claude, What generator are you using in your pipeline match? Can you show us the sitemap? You would need to use the Request generator or another one that 'loads' the pipeline with the contents of the HTTP Request. Cheers On 16/11/2007, Jean-Claude Vogel [EMAIL PROTECTED] wrote: Hello

Re: Custom DOM transformer

2007-11-16 Thread solprovider
The two examples are functionally equivalent. Both pipelines would error without the pattern=tentative match: the former because no pipeline match is found and the latter because no Serializer is called. The map:match element is irrelevant because the match must be assumed and no numbered