Hi! > The way I've implemented this sort of thing - getting request > parameters onto URLs pointing to JSF URLs - is by > hooking ViewHandler.getActionURL(). Would this > work for this scenario? > Good point, sure this might work too for the current scenario.
But then, in case of forms, they are put into the url like get parameters - which is mostly not wanted. And - once rendered the values are fixed, putting them on the link/button level allows the provider to return different values for different actions (once we extended the provider to tell him which component requires the values) You are right, with the component dependency problem, but I tend to make my life easier - thus - tomahawk extensions work only with tomahawk components. In the current case the user still can use the h:* components as their renderers are replaced by tomahawk. Ciao, Mario
