You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by David Rogers <da...@excira.com> on 2003/11/15 07:26:13 UTC

New ReadDOMTransformer/WriteDOMTransformer available?

Hi ,

>From bugzilla, it looks like (23921), Andrzej's 
New ReadDOMTransformer/WriteDOMTransformer, did not make it into
Cocoon 2.1.3? This seems like good functionality to have to me.
(read request scope doms)

Is this going to become part of cocoon? Is there a different way
to do achieve the same thing? Should I patch my own 2.1.3 with this
and carry on?


Thanks,
-Dave  






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: New ReadDOMTransformer/WriteDOMTransformer available?

Posted by Joerg Heinicke <jh...@virbus.de>.
On 15.11.2003 07:26, David Rogers wrote:

> Hi ,
> 
>>>From bugzilla, it looks like (23921), Andrzej's 
> New ReadDOMTransformer/WriteDOMTransformer, did not make it into
> Cocoon 2.1.3? This seems like good functionality to have to me.
> (read request scope doms)

No, it didn't make it as the bug is not fixed. You know, we all are a 
bit lazy, so higher the pressure on us to give your comments at the bug.

> Is this going to become part of cocoon?

Depends on the users. Comments like your one higher the chance of the 
bug of being applied.

> Is there a different way
> to do achieve the same thing? Should I patch my own 2.1.3 with this
> and carry on?

I suggest to "patch" your 2.1.3, what's really easy:

1. Download both files from the bug.

2. Copy them to COCOON_HOME/src/java/org/apache/cocoon/transformation.

3. Make a new build of Cocoon using "build webapp" or as you did it the 
first time. New files should make it without a "build clean webapp", but 
I don't know exactly (there is an uptodate check).

4. Open your sitemap and copy the declarations in the map:components 
section of your sitemap and change the class names there. Andrzej gave 
both classes a new name, so that you can use both old and new ones. So 
if you want to use both you have to rename either the new or the old 
ones, as the names must be unique.

Hope this works. And as I said it helps if you give your comments at the 
bug or at the list.

Joerg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org