Closed GoogleCodeExporter closed 9 years ago
Proposal is sound, but I believe the composite component is in such case just
the wrong tool for the puspose. If it's really a fixed parameter, you could
also add a <cc:attribute> for the parameter value.
Original comment by balusc
on 6 Jul 2013 at 4:12
It can be made a fixed parameter but in general this would need all possible
view-params to be added as composite attributes.
In some other composite components I just pass attributes for the purpose of
link creation to be inserted as `f:param` within `h:link`.
But these attributes are boilerplate if they only are used for this purpose.
Sometimes this are 3-4 parameters which are not used else in the component.
Original comment by releases...@googlemail.com
on 7 Aug 2013 at 1:24
Furthermore using <o:param> I need not only to add the view-params but also the
converter's ass attributes.
Especially necessary if the composite component is in a shared library where
many of those pass-through parameters would just overloading the interface
definition.
This can be usefull for static `<h:link>` aswell as my ajax approach.
Will post my method which is based on
http://code.google.com/p/omnifaces/issues/detail?id=235 later.
Original comment by releases...@googlemail.com
on 8 Sep 2013 at 1:32
Closing off as wontfix.
Feel free to reopen at GitHub if you've a more concrete real life example
https://github.com/omnifaces/omnifaces/issues
Original comment by balusc
on 17 Apr 2014 at 6:32
Original issue reported on code.google.com by
releases...@googlemail.com
on 28 May 2013 at 5:41