for me the example project and 2 were not enough... Unfortunately I do not have the config files at hand for at least one week to be able to show them to you.
3 depends on what functionality you have. The some of the jsf components did not work after switching to the icefaces ones. e.g. conversation switching, tabs in conversations, more than one declaration of identical stylesheets (I have them in more .xhtml files to see design time what they do). So YMMV.
Thanks, I don't have anything complicated in my xhtml Facelet files - sound like I should just make the leap...
I am looking at the instructions in the posted article, and also at the seam icefaces example.
I have started converting the web.xml, and I think I understand most of it. But I wonder what this part is for:
<!-- MyFaces --> <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener>
Does that have to do with the example code, or is it a requirement for ICEFaces configuration?
Forget the last post - I am tired - that was already in the web.xml, just in a different place...
Well, I managed to get all the jars and configuration done, and I am running my setup with ICEFaces turned on. I get a couple of weird effects:
- Between all page displays I get a popup box that shows for a very short time that says "Network connection Interupted - to reconnect click the reload button on the browser, or use the button below". But then the application continues.
- When hitting save in a simple form, I get an hourglass, the data is saved, but the hourglass never disappears.
Putting back the "Seam Redirect Filter" cured the problem with the hourglass being displayed and nothing else happening. No that part works as before.
Still having problems with the Network connection...
(BTW: I am running Seam 1.1.6.GA, and ICEFaces 1.5.3.)
Found this setting in another project that I gleaned at:
<context-param> <param-name>com.icesoft.faces.synchronousUpdate</param-name> <param-value>true</param-value> </context-param>
And - that cured the "Network connection interrupted" problem. (If someone can help me with what it means to have changed this setting I will be very greatful.)
After some quick testing, I think my app works as it did before the switch to using an ICEFaces configuration.