Nope, different stuff in T5. But this isn't implemented yet.
The ComponentEventDispatcher is pretty much ready for the job; it triggers and event on a component and captures the result object. There's a set of types that are supported for the return type ... currently Strings are considred Page Names (a redirect is sent), or Components are expected to be a page root component (a redirect is sent) but extending this list will allow for some additional types, such as some kind of MIMEByteStream type that represents a MIME type and an InputStream that can be pushed to the client. Details soon ... I'm writing a tutorial right now and I hope it will be ready before we start promoting 5.0.1 on monday. On 2/3/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 1/26/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > What I intend is to make it easy for components to generate links to > themselves, and allow an event handler method to return a bytestream > directly. None of this engine service complexity ... if a component > wishes to handle requests by generating a bytestream, I'll let it. Doesn't it need to interact with a Dispatcher? Like the AssetDispatcher which recognize the request asset prefix, or something like that? I was able to stream bytes to the client from wihtin a component and a page event handler method but always got some IllegalStateException when the container tried to manage the output via its own PrintWriter. I mean the whole process succeed but i fill the log with some nasty stack trace output, but probably i'm missing something... -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
