Programming to interfaces with beans?

2 Message(s) by 2 Author(s) originally posted in java programming

From: l-EE

Date: Tuesday, April 17, 2007

If I'm writting a bean

<programming> A {component architecture} for the {Java}
	programming language, developed initially by {Sun}, but now
	available from several other vendors.  JavaBeans components
	are called "{beans}".

	JavaBeans allows developers to create reusable software
	components that can then be assembled together using visual
	application builder tools including {Sybase}'s {PowerJ},
	{Borland}'s {JBuilder}, {IBM}'s {Visual Age for Java},
	{SunSoft}'s {Java Workshop} and {Symantec}'s {Visual Cafe}.

	JavaBeans support Introspection (a builder tool can analyze
	how a Bean works), Customisation (developers can customise the
	appearance and behaviour of a Bean), Events (Beans can
	communicate), Properties (developers can customise and program
	with Beans(?)) and Persistence (customised Beans can be stored
	and reused).

	{Home (http://www.javasoft.com/beans/)}.

	(1997-11-20)

- and I mean just a plain old JAVA Bean not an EJB

<specification, business, programming> (EJB) A {server}-side
	{component architecture} for writing reusable {business logic}
	and {portable} {enterprise} applications.  EJB is the basis of
	{Sun}'s {Java 2 Platform, Enterprise Edition} (J2EE).

	Enterprise JavaBean components are written entirely in {Java}
	and run on any EJB compliant server.  They are {operating
	system}, {platform}, and {middleware} independent, preventing
	vendor {lock-in}.

	EJB servers provide system-level services (the "plumbing")
	such as {transactions}, security, {threading}, and
	{persistence}.

	The EJB architecture is inherently transactional,
	{distributed}, {multi-tier}, {scalable}, secure, and {wire
	protocol} neutral - any {protocol} can be used: {IIOP},
	{JRMP}, {HTTP}, {DCOM} etc.  EJB 1.1 requires {RMI} for
	communication with components.  EJB 2.0 is expected to require
	support for RMI/IIOP.

	EJB applications can serve assorted clients: {browsers}, Java,
	{ActiveX}, {CORBA} etc.  EJB can be used to wrap {legacy
	systems}.

	EJB 1.1 was released in December 1999.  EJB 2.0 is in
	development.

	Sun claims broad industry adoption.  30 vendors are shipping
	server products implementing EJB.  Supporting vendors include
	{IBM}, {Fujitsu}, {Sybase}, {Borland}, {Oracle}, and
	{Symantec}.

	An alternative is Microsoft's MTS ({Microsoft Transaction
	Server}).

	{Home (http://java.sun.com/products/ejb/)}.

	{FAQ (http://java.sun.com/products/ejb/faq.html)}.

	(2000-04-20)

or
anything like that - is there any merit to seperating the interface

<jargon> A boundary across which two systems communicate.  An
	interface might be a hardware connector used to link to other
	devices, or it might be a convention used to allow
	communication between two software systems.  Often there is
	some intermediate component between the two systems which
	connects their interfaces together.  For example, two {EIA-232}
	interfaces connected via a serial cable.

	See also {graphical user interface}, {Application Program
	Interface}.

	(1996-05-22)

out of
the class

1. <programming> The prototype for an {object} in an
	{object-oriented language}; analogous to a {derived type} in a
	{procedural language}.  A class may also be considered to be a
	set of objects which share a common structure and behaviour.
	The structure of a class is determined by the {class
	variables} which represent the {state} of an object of that
	class and the behaviour is given by a set of {methods}
	associated with the class.

	Classes are related in a {class hierarchy}.  One class may be
	a specialisation (a "{subclass}") of another (one of its
	"{superclasses}") or it may be composed of other classes or it
	may use other classes in a {client-server} relationship.  A
	class may be an {abstract class} or a {concrete class}.

	See also {signature}.

	2. <programming> See {type class}.

	3. <networking> One of three types of {Internet addresses}
	distinguished by their most significant bits.

	3. <language> A language developed by the {Andrew Project}.
	It was one of the first attempts to add {object-oriented}
	features to {C}.

	(1995-05-01)

? I do this with pretty much every other kind of class I write

1. <chat> {Unix}'s simple {talk} command and {protocol}.
	write has been largely superseded by {talk} and then {irc}.

	An enhancement, {RWP}, has been proposed.

	2. <tool> A simple {text editor} for {Windows}.

	(1998-04-28)

but
Beans...

From: Edward Diener

Date: Tuesday, April 24, 2007

wrote in message:

If I'm writting a bean - and I mean just a plain old JAVA Bean not an EJB or
anything like that - is there any merit to seperating the interface out of
the class? I do this with pretty much every other kind of class I write but
Beans...

Just like any class, if you separate out the interface you can have
other developers implement the interface in order to extend

<programming> To add {features} to a program, especially
	through the use of {hooks}.

	"Extend" is very often used in the phrase "extend the
	{functionality} of a program."

	{Plug-ins} are one form of extension.

	(1997-06-21)

your
JAVABean ideas. Of course you might also want to provide an empty
implementation of the interface as a convenience class of those who just
want to extend the interface with just a subset of changes from the default.

Another advantage of separating out an interface, as a common idea, is
that you can have collections of the interface quite easily, and this
sort of collection will extend to other developers building JAVABeans
from your interface.

Next Message: this is wha i'm working on: any help???

Blogs related to Programming to interfaces with beans?

www : bugs
This is a symptom of long page names... one page in this Space is "Jack hated eating green beans. He thought green beans were the worst food in the world. He didn't know why anyone would want to eat them. There they sat in his plate. ...

Secrets of lightweight development success, Part 2: How to lighten ...
Instead of XML, Pico uses Java code to register beans in the container. Like Spring, Pico also supports setter injection, but the emphasis is strongly on constructors. Pico doesn't have nearly the amount of support that Spring has. ...

comp.lang.java.{help,programmer} - what they're for (mini-FAQ 2006 ...
An unmoderated group for discussion of Java as a programming language. Specific example topics may include: o types, classes, interfaces, and other language concepts o the syntax and grammar of Java o threaded programming in Java ...

Java/J2ee Interview Companion
TERM DESCRIPTION ACID Atomicity, Consistency, Isolation, Duration. aka Also known as. AOP Aspect Oriented Progamming API Application Program Interface AWT Abstract Window Toolkit BLOB Binary Large OBject BMP Bean Managed Persistence ...

Property Support - What Is The Use Case
Java should redefine a "bean direction", after all beans are about meta data and so annotations are a perfect fit here. Sun should write a single JavaBeans spec that would cover all platforms and unify the use of the word "bean". ...

Guice vs. Spring JavaConfig: A comparison of DI styles
This annotation tells Spring JavaConfig that the bean configured in the method is actually AOP advice that implements one of Spring's advice interfaces (such as MethodBeforeAdvice or even AOP Alliance's MethodInterceptor). ...