voyent
Woodstock to IceFaces JSF Portlet migration  XML
Forum Index -> Woodstock to ICEfaces Migration
Author Message
Tracker09

Joined: 12/May/2008 00:00:00
Messages: 14
Offline


I see that IceFaces is supplanting Woodstock as the preferred JSF component kit used in Netbeans. I also see that there are some tutorials provided that can be utilized to migrate and existing Woodstock application to IceFaces. My question is this. Can an exising JSF / Portlet Woodstock Application utilizing the JSF - Portlet Bridge be migrated to use IceFaces. I don't see this covered in the documentation. I do see that IceFaces can be used in a portlet environment. Has anyone been able to do this?
Sorry for the double post, I think this is a better category to put this post.
deryk.sinotte


Joined: 26/Oct/2004 00:00:00
Messages: 1008
Offline


It's true we don't have any portlet migration information in there. But, as we do support running in portlets, we'll see what we can do to remedy that.

The best way to start is to review the "Developing Portlets with ICEfaces" section of the Developer's Guide that comes with ICEfaces. It goes over all the things you need to know about building portlets using ICEfaces.

To address your question about the bridge directly is that the way ICEfaces supports bridging portlets to JSF is through an ICEfaces custom portlet. This is described in the documentation that I noted. You specify the ICEfaces portlet in your portlet.xml file like this:

Code:
 <portlet> 
   <portlet-name>toggleMessage</portlet-name> 
   <display-name>Toggle Message</display-name> 
   <portlet-class> 
      com.icesoft.faces.webapp.http.portlet.MainPortlet 
   </portlet-class> 
   <init-param> 
     <name>com.icesoft.faces.portlet.viewPageURL</name> 
     <value>/toggle.iface</value> 
   </init-param>
 </portlet>


Since we supply our own code for bridging, you would not include any other JSF-Portlet bridge libraries. In the future, we will be directing our efforts towards the standard JSF Portlet Bridge specification (JSR-301) so that our code is inline with other distributions.

The ICEfaces download also comes with a couple of sample portlets ([icefaces.dir]/samples/portlets/) including source code so you can see how to write ICEfaces portlets and how to take advantage of features like Ajax Push. Again, the documentation covers all of this so I'd encourage you to start there.

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
karinchen

Joined: 21/Nov/2008 00:00:00
Messages: 14
Offline


Hi!

In the meantime, is there any way to use the JSF 1.2 Portlet Bridge
Code:
 com.sun.faces.portlet.FacesPortlet
 

in an ICEFaces Portlets web application?
We are currently deploying on Liferay (latest Glassfish-Liferay bundle) and as soon as we change the ICEFaces to the JSF Portlet Bridge, our pages are unviewable (only some weird unreadable characters) on screen.

Thanks,
Karina
deryk.sinotte


Joined: 26/Oct/2004 00:00:00
Messages: 1008
Offline


Probably not. As I mentioned, the bridge that ICEfaces currently uses is our own MainPortlet. If you don't use that, then the logic it performs to adjust incoming portlet requests for the ICEfaces framework does not get executed, resulting in unpredictable (and likely unsuccessful) behaviour.

Is there a reason that you must use the JSF 1.2 Portlet Bridge? Because it should be possible to run ICEfaces portlets without it.

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
karinchen

Joined: 21/Nov/2008 00:00:00
Messages: 14
Offline


Thanks for the reply. We do actually right now successfully deploy portlets into Liferay using the ICEFaces portlet bridge and will perhaps come back with questions related to IPC.

--br,
Karina
 
Forum Index -> Woodstock to ICEfaces Migration
Go to:   
Powered by JForum 2.1.7ice © JForum Team