Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41F8FCE2.9010600@dotech.com>
Date: Thu, 27 Jan 2005 09:38:26 -0500
From: Irv Salisbury III <irv@dotech.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: Vadim Gritsenko <vadim@reverycodes.com>
CC: dev@cocoon.apache.org, Irv Salisbury III <irv@dotech.com>
Subject: Re: POST XML to cocoon protocol (with SAXBuffer)
References: <41F87656.2070205@dotech.com> <41F8BDE2.5070509@nada.kth.se>
 <41F8EDBE.20006@reverycodes.com> <41F8EEE7.3080002@dotech.com>
 <41F8F43A.5030309@reverycodes.com>
In-Reply-To: <41F8F43A.5030309@reverycodes.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Another thing to bounce off the list, hopefully something that I can 
give back.

Looking through the code, it seems like writing a 
RequestAttributeTransformer with the following functionality might be 
useful (at least to me :-)

1. Having the ability to use a org.apache.cocoon.xml.SAXBuffer to record 
SAX events and put an object of this class in as a named request 
attribute. 
2. Having the ability to pull a SAXBuffer out of the request as a named 
attribute and replay the SAX events. 

So, is SAXBuffer a good class to use for this, i.e. was it meant to be 
used for this? 
Am I missing something obvious?

Thanks,

Irv