|
Authored by: PJ on Saturday, April 21 2012 @ 10:12 AM EDT |
I have another question. I asked it late on an
earlier article, and I want to
ask it here. I
was sent this article years ago from on Sun's website:
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.
I don't know if it's still there. I
didn't check yet. But here's my question: is this typical of Java APIs? To
separate the design-only and the runtime classes and only ship the latter?[ Reply to This | Parent | # ]
|
|
|
|
|