It appears that the nesting of properties
("bean:nestedProperty:property") has been postponed for future
releases. That's unfortunate that it didn't make it into the 1.0 spec,
but I certainly won't miss the colon delimiter! Not being able to nest
properties makes jsp:getProperty pretty useless, IMHO. Did I mention
I'm in the anti-scriptlet camp?
Anyway, I just wanted to remind everyone about a few JavaBean things
that might not be important now, but I think will be important in a few
months when you might start to see visual development of JSP pages.
That is, the tag
<jsp:getProperty name="bean" property="prop" />
does *not* necessarily translate to
<%= bean.getProp() %>
and (JSP 0.92)
<DISPLAY PROPERTY="bean:nestedBean:prop">
does *not* necessarily translate to
<%= bean.getNestedBean().getProp() %>
One of the features of JavaBeans is that you can create a BeanInfo
class that contains the meta-information for the bean. You can, in
fact, choose exactly which properties you want to expose and even the
read/write methods for each of those properties. The getX()/setX()
naming conventions are used by the Introspector only when the BeanInfo
class isn't present.
I know it's a stretch right now to think that we'll be delivering
BeanInfos with our JSP beans right now, but we've got a nice framework
in JavaBeans that we should leverage as much as possible. Thanks for
listening.
--
Eric Lunt
mailto:[EMAIL PROTECTED] Ph: 312-642-9050 Fax: 312-642-9051
Burning Door, LLC (http://www.burningdoor.com)
"Helping our clients build effective web applications"
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
