I've put up the home page, as http://howardlewisship.com/tapestry-prop/
I don't have a download for this yet; eventually, it will be
distributed via maven. For the moment, it requires a quick download of
the source via SVN and build via Maven2.
I expect to add support for complex properties ("foo.bar.baz") before
a final 1.0 release.
On 11/20/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> I'm squandering some cycles on tapestry-prop, which adds a "prop:"
> prefix. It makes the cost of a single "hop" drop by a factor of 10 or
> so.
>
> I hope to expand it to support simple property paths, i.e.,
> "foo.bar.baz" would expand, automatically, to
> "getFoo().getBar().getBaz()" (or setBaz(), as appropriate). That does
> open up new questions about handling nulls, as well as special cases,
> such as java.util.Map.
>
> I'm looking for some kind of 80/20, where most of the time, you can
> use prop:, and swich to ognl: only when you need a little more
> expressive power.
>
> The joy of Tapestry 4.0 is that these changes don't need to wait for
> 4.1, or delay 4.0. Just include the tapestry-prop library on the
> classpath and the configuration meshes together, care of HiveMind.
>
>
>
> On 11/20/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> > I should also point out that (still more) slogging through the bowels of
> > tapestry databinders and OGNL has convinced me that the combination isn't
> > quite as clueless about static as I imagined. A truly static binding is
> > still faster than an "ognl:@[EMAIL PROTECTED]" binding, but a static
> > ognl binding is quite a bit faster than a dynamic one as Howard (and OGNL)
> > try to only resolve it once.
> >
> > So performance goes:
> >
> > "Monday" >> "ognl:@[EMAIL PROTECTED]" >> "ognl:getToday()"
> >
> > --- Pat
> >
> > > -----Original Message-----
> > > From: Leonardo Quijano Vincenzi [mailto:[EMAIL PROTECTED]
> > > Sent: Saturday, November 19, 2005 11:52 PM
> > > To: Tapestry users
> > > Subject: Re: Ways to Make OGNL Run Faster
> > >
> > > Now for the obvious question... what plans are there to make this
> > > transparently faster? I mean, if the framework lets you put
> > > "foo.bar.x.y.z.help" in an ognl expression, it must take every step
> > > possible to make that as fast as a single "getHelp()" instruction. I
> > > mean, if Hibernate can do it, why OGNL can't?
> > >
> > > Maybe Tapestry can learn from other frameworks. Though I'm specially
> > > worried about start-up and compilation time on devel mode, more than
> > > runtime performance (but maybe that's because I'm not requiring my
> > > web-apps to handle millions of users, not right now).
> > >
> > > --
> > > Ing. Leonardo Quijano Vincenzi
> > > Director Técnico
> > > DTQ Software
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta 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]
