> After a while of using Ajax4Jsf, I am really liking how they > handle component rendering resources (JavaScript and CSS > files mainly). Their method seems to be cleaner and (I think) > have better performance than Tomahawk.
Both implementations suck when it comes to portlets. Portlets generate full html pages, so from the JSF point of view either approach sticks in the necessary resources. But the portal strips all of these when it is finally rendering the full portal page. The only solution I've found is to extract the resources from tomahawk (whatever), and promote the resources to full citizen status within the portal. So, for example, instead of just including tree.js on pages where I've got an embedded <t:tree2 /> tag, I must include tree.js in the portal template for all pages (whether they have <t:tree2 />'s or not). Granted this is an issue for the generation of portlets, but it is a big pain in the butt to have to track down these resources when they get embedded into the binary jars of the distribution. I'm hoping this issue is somewhat resolved in JSR 268, but I'm certainly not going to hold up my project waiting for a better solution...
