Re: Bean ancestry

Article View: borland.public.jbuilder.java.api

Article #3244

Back to borland.public.jbuilder.java.api Previous Next

#3244

From: Paul Furbacher
Date: Fri, 27 Mar 1998 00:00

19 lines
1364 bytes

Steven Feinstein wrote:
> 
> While using another IDE, I found out that all beans had to be inherited
> from java.awt.compoenent.  Does JBuilder also have this limitation?  I'm
> trying to create invisible beans (database access, business rules) and they
> do not need an interface.

If you look at a component such as "TextDataFile", it is
a bean, can reside on the palette, but doesn't have any
visible representation in the Designer.  You can select
it in the Structure pane's treeview, and its properties
will be displayed in the Object Inspector.  

So, no, beans don't need to descend from awt.component.
Check out the ancestry of various classes in the JBCL
using the on-line help to prove this to yourself.

Paul Furbacher

Technical Details

Message-ID: <351BA155.4A34@bilbo.bio.purdue.edu>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <01bd59a3$d13b2ee0$ed4045a7@W018134>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1089d0,24910275a85597e5
X-Google-Attributes: gid1089d0,public
From: Paul Furbacher <pf@bilbo.bio.purdue.edu>
Subject: Re: Bean ancestry
Date: 1998/03/27
Message-ID: <351BA155.4A34@bilbo.bio.purdue.edu>
X-Deja-AN: 338320386
Content-Transfer-Encoding: 7bit
References: <01bd59a3$d13b2ee0$ed4045a7@W018134>
To: Steven Feinstein <SteveFeinstein@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Organization: Biological Sciences, Purdue Univ.
Mime-Version: 1.0
Reply-To: pf@bilbo.bio.purdue.edu
Newsgroups: borland.public.jbuilder.java.api

Reply to Parent Message