Re: Java Bean Question
Daniel Pitts wrote:
Lew wrote:
Primarily to be a JavaBean means to follow the convention that there
is a getX() and setX() for all properties X, except booleans which
have an isX() and setX() method.
[snip]
Just follow the accessor (getX() or isX()) and mutator (setX()) method
conventions for all attributes and your class will work with JSPs just
fine for scope less than session.
<soapbox relevancy="not for OP">
This is one of the most pervasive misconceptions about any part of Java.
JavaBeans aren't just about convention! The spec actually allows you
to override the names of the getter/setters that go a property. There is
also the concept of different "views" of the bean. For a beginner, its
fine just to use the "conventional" approach to JavaBeans, but its
amazing how many "professional" tool sets implement their own bean
accessing through the Reflection API and get the spec WAY wrong.
</soapbox>
Sorry, just a pet peeve of mine. JavaBeans are far more than POJO, but
many people seem to dismiss that. Ohwell :-)
You raise very important points, albeit beyond the scope of what the OP needs.
Sometimes it's better to take a simplified explanation, as I did, rather
than try to lay out all the complexities of the JavaBeans specification.
Obviously you see this, given your remarks "for a beginner".
For the so-called "professional" tool sets a higher standard does apply. I
commend you for calling attention to the more advanced issues.
For those that needed the full story, I did provide the link to the
specification, repeated here so others will not make the sort of mistake you
described:
<http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&PartDetailId=7224-javabeans-1.01-fr-spec-oth-JSpec&SiteId=JSC&TransactionId=noreg>
--
Lew