tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Lewis-Shell" <rlewissh...@mac.com>
Subject Re: Why enhance direction="custom" binding properties?
Date Mon, 22 Dec 2003 21:47:09 GMT
Ah - you mean if I have a foobar parameter (direction="custom") with no
abstract get/setFoobarBinding property and then my component uses an OGNL
expression: "foobarBinding.object"?

Yes, this would be a runtime problem under this suggestion, but if there is
no abstract method, it seems entirely reasonable to me to use:
"bindings.foobar.object" instead.

R

----- Original Message ----- 
From: "Harish Krishnaswamy" <hkrishnaswamy@comcast.net>
To: "Tapestry development" <tapestry-dev@jakarta.apache.org>
Sent: Tuesday, December 23, 2003 10:20 AM
Subject: Re: Why enhance direction="custom" binding properties?


> What if the property is bound to an embedded component in the template or
specification?
>
> -Harish
>
> Richard Lewis-Shell wrote:
>
> > "All formal parameters now get a specific binding property"
> >
> > Why is this necessary?  If there is no abstract method, then no code can
> > depend on the getter/setter that Tapestry will add (can it?), so what is
the
> > benefit of this enhancement.
> >
> > (I am now thinking that if there is no abstract method AND the Direction
is
> > custom, then an enhanced binding property is not needed)
> >
> > Thanks,
> >
> > R
> >
> > ----- Original Message ----- 
> > From: "Howard M. Lewis Ship" <hlship@comcast.net>
> > To: "'Tapestry development'" <tapestry-dev@jakarta.apache.org>
> > Sent: Tuesday, December 23, 2003 10:05 AM
> > Subject: RE: Why enhance direction="custom" binding properties?
> >
> >
> >
> >>Tapestry is creating a property to store the binding.  All formal
> >
> > parameters now get a specific
> >
> >>binding property. When direction is not "custom", it will add additional
> >
> > properties to get at the
> >
> >>binding's value.
> >>
> >>--
> >>Howard M. Lewis Ship
> >>Creator, Tapestry: Java Web Components
> >>http://jakarta.apache.org/tapestry
> >>http://jakarta.apache.org/commons/sandbox/hivemind/
> >>http://javatapestry.blogspot.com
> >>
> >>
> >>>-----Original Message-----
> >>>From: Richard Lewis-Shell [mailto:rlewisshell@mac.com]
> >>>Sent: Monday, December 22, 2003 3:29 PM
> >>>To: tapestry-dev@jakarta.apache.org
> >>>Subject: Why enhance direction="custom" binding properties?
> >>>
> >>>
> >>>I am trying to figure out why all of our components are
> >>>getting enhanced,
> >>>even though our code still only uses the 2.2 feature set.  We
> >>>almost always
> >>>use custom direction parameters, and the classes generally access the
> >>>bindings using getBinding("someParameterName") rather than declaring
> >>>get/setSomeParameterName() methods.  Yet, scanForBindingProperty() in
> >>>ComponentClassFactory will create an enhanced property for a binding
> >>>regardless of its direction.  scanForParameterProperty() does NOT - it
> >>>checks for Direction.CUSTOM, and aborts in that case.
> >>>
> >>>Should Tapestry create an enhanced binding property for
> >>>direction="custom"
> >>>parameters?  If so, why?
> >>>
> >>>I am still coming to grips with class enhancing, but, at this
> >>>stage, I am
> >>>thinking - no, custom should mean 'hands off - I know what I'm doing'.
> >>>
> >>>R
> >>>
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >>>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >>>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >>
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message