tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard Lewis Ship" <hls...@gmail.com>
Subject Re: [jira] Closed: (TAPESTRY-1370) Add a component event result processor for Class instances
Date Fri, 08 Jun 2007 15:35:16 GMT
That's a good point ... should we just get rid of String response?

I'm not certain; there may be some cases (such as the forthcoming
Spring Web Flow integration) where strings would be more
useful/convienient than Class instances.

On 6/8/07, Massimo Lusetti <mlusetti@gmail.com> wrote:
> On 6/8/07, Davor Hrg <hrgdavor@gmail.com> wrote:
>
> > it seems that by adding the class resolver string response becomes obsolete
> > for resolving pages,
>
> FWIW I couldn't agree more.
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message