Chris wrote:
Part II in what's threatening to be my Pedantic Bean Series . . .
[...]
Does JSP really only work with Beans (and not just plain Jane classes),
and is the JSWDK just being nice (and if so what kind of a reference
implementation is it? OR is there no Bean requirement at all -
Hi Chris,
I think the only real requirement for the 'class' implementing the
'object' referred in the useBean:... tag is that properties should
be
get-able and set-able for the setProperties tag to work as
defined in the spec. One can't be too sure if some implementation
would use the fact that
PROTECTED] mailto:[EMAIL PROTECTED] )
-Original Message-
From: Chris [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, July 07, 1999 10:31 PM
To: [EMAIL PROTECTED]
Subject: Beans? Really? Are you sure?
Part II in what's threatenin
Let me see if I can help clear up the confusion.
A Java Bean is just a class which follows some basic rules to be considered
part of the JavaBeans component model. A Java Bean also has access to some
basic services which are part of the JavaBeans architecture and API but that
isn't important
Let me see if I can help clear up the confusion.
...
The reason JSP states that it uses Java Beans, instead of plain
ol classes, is
because the JSP environment expects that the classes used in the
jsp:useBean
tag adhere to the basic bean requirements.
...
One more little thing you might want
Part II in what's threatening to be my Pedantic Bean Series . . .
When I first read about JSP, and I found out that they use Beans (not
classes but Beans), I shit myself. Okay, no I didn't, but I was
displeased because I actually have been a semi-successful freelance Java
coder since the week
