For what it's worth, "embedded properties" are exactly how
WebMacro works. It's also more aggressive than the bean spec
about introspecting objects. For example, it's willing to
loop with iterators or enumerations, and also
$Foo.Bar.Baz
can be extracted from Foo.getBar("Baz"), which is useful for
things like getHeader("Cookie:) and such.
http://webmacro.org
Justin
Quoting h wulfson ([EMAIL PROTECTED]):
> --- Brad Neuberg <[EMAIL PROTECTED]> wrote:
> > Even though embedded
> > properties "technically"
> > violates good object-oriented encapsulation, it
> > makes for much more
> > readable and createable code. For example, tell me
> > which is more
> > readable:
> >
> someObject.getProperty1().getProperty2().getProperty3()
> > someObject.Property1.Property2.Property3
> >
>
> To answer your redundant question, the embedded
> properties are more readable and writable, and it
> doesn't really violate OO encapsulation: the
> properties can still only be exposed through
> getter methods.
>
> -Harris
>
> _________________________________________________________
> Do You Yahoo!?
> Free instant messaging and more at http://messenger.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".
===========================================================================
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".
