Should we consider deprecating t:updateActionListener in 1.2 and removing it in 2.0 now that f:setPropertyActionListener exists?
Perhaps for 1.2, we should consider making the tag an alias for f:setPropertyActionListener component rather than a separate component. As far as I know, there is no intentional difference in behavior between the tomahawk component and the core component. I know for facelets that f:setPropertyActionListener is facelets-aware and works better for passing objects between template fragments. I'm pretty sure that you can change the underlying object using f:setPropertyAL and have it reflected in the caller, but you cannot do so with t:updateAL as this was why I ended up switching over all of my code a few years back.
