Peter Donald wrote:
[snip]
> Personally I hope the component library encourages JavaBeans (or
> equivelent) type access as primary importance.
+1000 !!! It's all the other stuff (lifecycle and configuration, and so on) that
distinguishes frameworks from each other. That stuff doesn't belong in the
component library.
Quick acid test for inclusion -- check the import statements for
"org.apache.struts.*" or "org.apache.turbine.*" or "org.apache.avalon.*", and Just
Say No (TM).
> Other framework specific
> access patterns (regardless whether they are turbine/avalon/struts/other)
> should be discouraged and only allowed while the component is being
> refactored. Once it hits release/stable/whatever status I hope/believe
> JavaBeans will be dominant modelling paradigm (or something like Ant thats
> is also relatively lightweight).
>
There are also lots of development tools already that know about JavaBeans
programming conventions, as well as code generators to do all manner of the
mundane part of the development effort.
>
> Cheers,
>
> Pete
>
Craig
