About 18 months ago, I participated in a webcast of a online meeting sponsored by IceSoft. At the time, I understood that there was a limitation when using IceFaces, where a page using IceFaces components cannot have any other kinds of components on the page. I may have misunderstood this limitation, and would like it to be clarified...can a page hosting IceFaces components have any other kind of component on the page, such as a RichFaces component or a custom component? If so, are there any limitations in the use (location on the page, etc) of the other component or the IceFaces component? If not, are there any plans for this to be available in a future version of IceFaces?
Thanks in advance for your response.
Joined: Jan 24, 2009
Still an interesting question. Indeed it depends. If you mix pure JSF frameworks you will have no problems. But, RichFaces has AJAX, and that is why you can't use both in parallel. The current AJAX frameworks, every JSF framework uses a different one, are almost not compatible to each other. This is the real problem. The position you use tags in a page is not the problem. The tags have to be unique. This is normally done through namespaces. Here's an example of my book code:
This is templating based on Facelets. The namespaces in the HTML tag show that you can mix a lot by default. The last namespace defines the Facelets components I wrote for the book.
Pretty interesting is the Tomahawk entry. ICEsoft has an integration project to allow a mixture of ICEfaces and the Apache components in your project. Although, the Tomahawk components will not support the CSS skinning of ICEfaces components. But, if you dislike the ICEfaces tree component e.g. you can use the Tomahawk one ;-). However the integration is not 100%, maybe the architectures behind are a bit too different in the end.