Love Roberts POJO comments. I have always found it hypocritical, that
the Hibernate guys managed to kill off JDO, partially using the
argument that JDO use post processing to enhance classes so they are
not pure "POJO". Then Hibernate found out that reflection performance
sucked and switched over to using runtime byte code enhancement. Now
how is that session connected, byte code enhanced subclass a POJO.
I am not saying that the concept of a POJO is bad, but imagine trying
to build a Swing application with POJO's where you had to use
annotations for everything.
regards Malcolm Edgar
On Fri, Nov 20, 2009 at 3:54 AM, Michael Gentry <mgentr..asslight.net> wrote:
> Maybe I'm just disagreeable today ... :-)
>
> I like autocomplete, especially as a new user to a framework, showing
> me what I can/should override. With T5 I have to hit the
> documentation and guess. Do I need setupRender() or pageAttached() or
> ... With autocomplete, I at least can see a list of methods to help
> me get started in that process (and see the JavaDocs for each one to
> decide which method to try). And, since the source code is available
> if you inherit functionality, you can easily look at it and see
> precisely the order things are called. Automagic methods are much
> more sealed off.
>
> Thanks,
>
> mrg
>
>
> On Thu, Nov 19, 2009 at 10:19 AM, Robert Zeigler
> <robert.zeigle..uregumption.com> wrote:
>> *I have enjoyed Tapestry 5's "POJO" approach to development, but even there,
>> I enjoy it more as a committer, for the flexibility it affords in evolving
>> the framework, than as a user. The only real bonus as a user is that
>> autocomplete works a lot better since the only methods in the class are the
>> ones I've defined, rather than a bajillion superclass methods. ;)
>
This archive was generated by hypermail 2.0.0 : Thu Nov 19 2009 - 17:52:12 EST