Re: JavaBeans
On 23.07.2011 17:23, Stefan Ram wrote:
markspace<-@.> writes:
I suspect we are missing some context here. Not all Java beans uses
have worked out. Is there a link to your source?
Yes, I found it!
|Date: Sun, 10 Jul 2011 13:34:19 +0100
|From: Tom Anderson<twic@urchin.earth.li>
|Subject: Re: Spring/hibernate and JDBC
|(...)
|Waitwhat? Tools composing applications out of JavaBeans? Wasn't that idea
|dead in, like, 1998? What the hell is going on here? Is there some mad
|backwater Lost World of Java development where people are actually
|building apps by dragging icons around in tools?
<disclaimer>I do not overlook the whole Java industry.</disclaimer>
I think what this refers to is the aspect of JB to have a bean bundled
together with a GUI component and that this can be used to configure the
bean for use. I have never seen this done but then again I'm mostly
under way on server side.
If there are some examples where that approach has been used
successfully (or even used at all) I'd be interested to hear them.
When looking for reasons why there is no widespread adoption then maybe
we have to look at general issues with component based development - and
here I mean that version of CBD where you go into a store and buy
components from different vendors with the functionality you need and
then you "only" plug your application together. Of course there are a
lot of components around (some view every class as a component) but in
my experience they are usually created by one team.
Several other aspects of JB (for example: properties) are widely in use
and in fact a whole lot of other standards and tools rely on the
property accessor naming convention.
Kind regards
robert
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/