[
https://issues.apache.org/jira/browse/TAPESTRY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568262#action_12568262
]
Kevin Menard commented on TAPESTRY-1764:
----------------------------------------
I meant to add in my two cents on this issue after raising a question about
mixins on the user list. The key point from that was the following:
"What I'm looking to do is is basically a value filter. I'd like the mixin
to take the value, apply its filter, and pass on to the next mixin or
component in the chain. I've actually got several other candidate
operations in mind as well (truncation, capitalization, URLification)."
In my case, I'm not actually looking to modify any bound values, so nothing
would change behind the scenes -- I agree that that's a situation looking to
explode and would be incredibly frustrating to debug. What I want to do is
intercept the supplied value from a mixin and then pass that value onto either
the next mixin or component. A read-only access to the bound value would get
us half-way there, but there are obvious problems with mutable state. While
there are certainly a lot of problems that could arise there, enough sign posts
have been placed by then that a mixin author really should know what he ought
and ought not be doing.
> provide access to component parameters from within mixins
> ---------------------------------------------------------
>
> Key: TAPESTRY-1764
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1764
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Kristian Marinkovic
>
> A mixin can't access the parameters of a component because the Bindings
> property of the InternalComponentResourcesImpl class is private and the
> respective interface does not provide a access method.
> I was trying to create a mixin that would render only the value of a form
> element (without the tags) when it was in a certain state. There also might
> be use cases where mixins are used to collect data from the components they
> are attached and therefore also needs access to the components parameters.
> see threads:
> http://www.nabble.com/Antwort%3A--T5--how-to-read-the-value-of-a-component-parameter-within-a-mixin-tf4487995.html
> http://www.nabble.com/-T5--how-to-read-the-value-of-a-component-parameter-within-a-mixin-tf4487597.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
