So, i only just took a look at EmbeddedComponentAssemblerImpl which seems to be the place that does the mixin assembly and i noticed there's not much difference with how implementation and instance mixins are registered.
That got me thinking and i figured there's no visible reason why implementation mixins can't use parameters - so, i created a quick test and indeed parameters work (both in 5.3.0-SNASHOT and 5.2.4). That basicaly means that the docs at http://tapestry.apache.org/component-mixins.html are incorrect (or that the phrase "Note that Tapestry currently doesn't support parameters in implementation mixins" refers to something else??) Interestingly, the 5.1.0.5 docs at http://tapestry.apache.org/tapestry5/guide/mixins.html don't mention any such limitation! Finally, https://issues.apache.org/jira/browse/TAP5-13 was resolved at some point and can now safely be closed. I'll go on and update the docs and jira in a day or two... On Wed, Feb 23, 2011 at 17:52, Andreas Andreou <[email protected]> wrote: > thx, i'll try to add support for this then > > On Tue, Feb 22, 2011 at 19:06, Howard Lewis Ship <[email protected]> wrote: >> On Tue, Feb 22, 2011 at 4:10 AM, Andreas Andreou <[email protected]> wrote: >>> Short version: >>> Why doesn't Tapestry support parameters in implementation mixins? >>> Is it something that's just not yet written, or is there something that >>> would >>> make this infeasible? >>> >> >> Just not yet written. >> >> >>> Long version: >>> So, i've started doing some T5 work at last :) ... and came >>> across the ZoneUpdater mixin >>> ( http://tinybits.blogspot.com/2010/03/new-and-better-zoneupdater.html ) >>> which looks interesting and useful enough to be included in T5. >>> >>> I then noticed https://issues.apache.org/jira/browse/TAP5-1415 >>> (which is basically an unintented consequence of introducing a zone >>> parameter to the Select component ... makes existing zoneupdater >>> user code fail) which made me took a look at the zone related code in >>> Select. It seems to me that what happens there is just a special >>> case of ZoneUpdater (for instance zoneupdater can connect to >>> any clientside event, and it can pass extra context params). >>> >>> Anyway, assuming that something like ZU is introduced as a mixin in T5, >>> it should be possible to remove the zone related code of Select and reuse >>> ZU if it wasn't for that implementation mixin limitation. >>> >>> -- >>> Andreas Andreou - [email protected] - http://blog.andyhot.gr >>> Apache Tapestry PMC / http://chesstu.be owner >>> Open Source / JEE Consulting >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > Andreas Andreou - [email protected] - http://blog.andyhot.gr > Apache Tapestry PMC / http://chesstu.be owner > Open Source / JEE Consulting > -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Apache Tapestry PMC / http://chesstu.be owner Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
