|
Authored by: PJ on Saturday, April 21 2012 @ 02:06 AM EDT |
I have a question, then. Read this first please:
Introduction to the
JavaBeans API: Short Course
The JavaBeans architecture is the standard
component architecture for Java technologies. The complete JavaBeans API is
packaged in java.beans, one of the core Java APIs. This package includes
interfaces and classes that support design and/or runtime operations. In
developing a JavaBeans component, it's common to separate the implementation
into design-only and runtime classes, so that the design-oriented classes (which
assist programmers during component assembly) do not have to be shipped with a
finished application. The JavaBeans architecture fully supports this
implementation
strategy.
http://java.sun.com/developer/onlineTraining/Beans/JBeansAPI/shortc
ourse.html
Is that true only about JavaBeans or is it true of all
the APIs that the "design-only" classes do not ship with a finished application?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, April 23 2012 @ 08:48 AM EDT |
> Java doesn't have "headers" or separate interface
> definition files.
It can do.
See http://docs.oracle.com/javase/tutorial/java/IandI/createinterface.html
That page has quite an informative section entitled "Interfaces as
APIs" which would appear to blow large holes in Oracle's current case :-)
[ Reply to This | Parent | # ]
|
|
|
|
|