Sounds good.

You've probably already thought about this, but you might want to make the
new default binding handle true/false... completely replacing OGNL with
tapestry-prop in Tap4 has involved adding the following two examples of
brilliant design to my base component class:

public boolean getTrue() { return true; }
public boolean getFalse() { return false; }

On 9/4/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:

It isn't just the use of reflection, its the amount of synchronization
involved.

For Tap5, OGNL will be an add on. I've already coded the first pass at a
prop: binding, as the default, for Tap5.  It may get smarter, and support
simple property paths as well as property names. Anything more complex
will
require OGNL ... or a synthetic property in Java code (with component
class
refreshing, that's just as easy and much faster at runtime).

A lot of what OGNL buys you can be replaced with Java code in Tapestry 5.
OGNL does do a lot of other very useful things, such as method invocation,
collection selection and projection, and class/collection instantiation.
But
a large percent of the time, using OGNL for single property access is
overkill (even in Tapestry 4).

On 9/4/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
>
> Death to OGNL!
>
> Seriously though, recent replacement of OGNL with tapestry-prop halved
> component rendering times for me. It's nice that Tapestry scales better
> than
> other frameworks, but baseline speed is important, too...
>
> On 9/4/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> >
> > Several of the dependencies are not Apache projects. Apache guidelines
> (to
> > my knowledge) forbid distributions that include non-Apache files.  Or
it
> > may
> > be non-ASL files.  I know that Jesse has been working with the Dojo
> folks
> > to
> > support redistribution of their stuff.   OGNL and Javassist (both MPL)
> are
> > the real sticking points here.
> >
> > On 9/3/06, andyhot <[EMAIL PROTECTED]> wrote:
> > >
> > > we currently have 2 distributions:
> > > - tapestry jars + source
> > > - tapestry documentation
> > > Those apply to 3.0.4, 4.0.1, 4.0.2 and 4.1(no docs here)
> > >
> > > Any reason why we can't add another one having all deps included -
> > > making it
> > > easier for newcomers to use?
> > >
> > > --
> > > Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / J2EE Consulting
> > >
> > >
> > >
---------------------------------------------------------------------
> > > 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
> >
> >
>
>


--
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


Reply via email to