-
1. Re: WebUI portlet tutorial
theute Jan 12, 2010 11:36 AM (in response to ybilas)1 of 1 people found this helpfulWebUI is mostly for internal portlets (the one we ship). One benefit is that what we use will not collide with what you use.
For your portlets you can choose your framework, I would recommend JSF with the use of the JBoss Portlet Bridge.
-
2. Re: WebUI portlet tutorial
ybilas Jan 12, 2010 2:56 PM (in response to theute)Thanks for the clarification.
I am a newcomer to the portlets world, so to me it doesnt matter which framework to learn, but I was under the impression that the webui would be a primary choice for portlet development, considering its wide range of features. Any other reason NOT to use it, other than possible collisions?
Also, what would it take to use ICEFaces with gatein? Is jboss portlet bridge needed?
Cheers.
-
3. Re: WebUI portlet tutorial
claprun Jan 12, 2010 7:17 PM (in response to ybilas)1 of 1 people found this helpfulAs you mentioned, WebUI is not well documented at this time. It's been developed mostly for internal use so it's quite rough along the edges. It's probably not as straight forward as JSF for portlet development at this time. The main reason not to use it, in my mind, though, is that it will make your portlet completely tied up to GateIn as WebUI only runs on GateIn. It's also not supported whereas JBoss' portlet bridge is/will be. I'm not sure about ICEFaces support in portlet bridge but you should be able to use RichFaces and Seam without issues.
All in all, I would really recommend using JSF to develop your portlets.