|
Authored by: jbb on Saturday, April 21 2012 @ 11:18 AM EDT |
[I]s this typical of Java APIs? To separate the design-only and the
runtime classes and only ship the latter?
No, not really. This is
a JavaBeans thing. I'm not an expert on JavaBeans but I see them as an attempt
to make Java more like Microsoft's Visual* languages where you can use a GUI to
create code. This is why there are "design-only" components. If someone wants
to use a GUI to create a program using parts from your JavaBean then they will
need to use the "design-only" components. You won't need them to run the final
application or to program the old fashioned way.
I don't think it is
relevant to the case but I think it was an astute question because the answer is
non-obvious.
--- Our job is to remind ourselves that there are more
contexts than the one we’re in now — the one that we think is reality.
-- Alan Kay [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, April 21 2012 @ 01:24 PM EDT |
"If you have used Delphi, or Visual Basic, you are already familiar with
the notion of a bean. The idea is the same; the programming language is
different. A Java Bean is a reusable software component that works with Java.
More specifically: a Java Bean is a reusable software component that can be
visually manipulated in builder tools. "
"Disadvantages: Having to create a getter for every property and a setter
for many, most, or all fields, creates an immense amount of boilerplate
code."
It is sort of related to reflection, in the sense that, you could query a server
with "send some stuff".
You get some stuff back.
It's just a blob, you don't know what it is, you don't know what it does, you
don't know what it is in it, or what you can do with it.
With one very important exception, because it is a Bean, you can query it to
find out everything that you need to know about it and the blob itself contains
everything you need to manipulate it, specifically, not only everything you need
to manipulate it in your program(run-time), but everything you need to
manipulate it in your Integrated Development Environment(Design), even if your
development environment has never been exposed to anything like it before.
[ Reply to This | Parent | # ]
|
|
Authored by: BobinAlaska on Saturday, April 21 2012 @ 04:32 PM EDT |
PJ,
It is still there with an Oracle logo on it now.
---
Bob Helm, North Las Vegas, NV
[ Reply to This | Parent | # ]
|
|
|
|
|