Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <3F2791DE.8050304@che-che.com>
Date: Wed, 30 Jul 2003 11:37:34 +0200
From: Juan Jose Pablos <cheche@che-che.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.2.1) Gecko/20030311 Debian/1.2.1-10
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: xsl:output
References: <3F25356A.9090505@che-che.com>
 <20030729053741.A77E874F8F@smtp.us2.messagingengine.com>
 <3F262D0C.4050206@che-che.com>
 <20030729133146.BC8CF7372A@smtp.us2.messagingengine.com>
 <3F276692.90603@che-che.com>
 <20030730092846.17BB96FB96@smtp.us2.messagingengine.com>
In-Reply-To: <20030730092846.17BB96FB96@smtp.us2.messagingengine.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Upayavira,

Upayavira wrote:
> 
> Niether. It is by design. The <xsl:output> tag assumes that the
> transformer is responsible also for serialization. However, in Cocoon
> these have been separated into two different components. As the
> transformer doesn't handle serialization, tags that are there to handle
> it are ignored.
> 
> Make sense?
> 
> Regards, Upayavira

Maybe I am saying something stupid, but why the serializer does not take 
that responsability?

I mean, I happy as long I can make it happend, but I know that people 
expect xsl:output to work
Cheers,
Cheche