tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Kuhnert" <jkuhn...@gmail.com>
Subject Re: BeanForm Move
Date Tue, 11 Jul 2006 01:42:06 GMT
Ahh....I hadn't noticed that you had added in validation handling. Looks
pretty slick so far.

I worry about adding components into the library unless an active committer
is going to take responsibility for maintaining them - and the likely JIRA
issues they produce...But I guess even worse than that is not applying
patches that look good so...

Can you create a new patch that works off of tapestry 4.1 trunk ;) ?

P.S. Something came over me and I think I found a pretty easy way to make a
small modification to OGNL that would make it possible to definitively know
a target properties type, even if it is null. The only problem is that OGNL
seems to be in the hands of opensymphony/webwork right now and I've not seen
much response to any forum posts I've written. Oh well...

On 7/10/06, D&J Gredler <djgredler@gmail.com> wrote:
> Hi,
> I just wanted to send the list a quick heads up in view of our previous
> discussion: I've moved BeanForm to a separate SF project (
> http://beanform.sourceforge.net/), uploaded it to Tassel, and have marked
> the patch (http://issues.apache.org/jira/browse/TAPESTRY-965) obsolete. I
> still think this would be a useful component to have in Contrib, and can
> create an updated patch at some point in the future.
> I think I've addressed all the issues raised in previous discussions on
> this
> list (see the docs at the website), but would be happy for any further
> critique. This applies especially to the rendering hierarchy. Thanks for
> all
> the advice and direction given thus far.
> Take care,
> Daniel Gredler

Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message