ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

OK Thanks, the problem is now solved, thank to the developper guide of icefaces.
To be honest I'm a bit surprised the lifecycle of the portlet can be so ignored. I also have problems with EDIT mode (preferences editing). My form cannot be sumbitted (actionlistener never called) in this mode. In the view mode I have no problem with the same form. It seems to me that icefaces classes are not aware of the portlet mode, the APIreacts just as if the page I'm facing is the previous page (I mean the page I was in when I clicked on the "edit preferences" button). Indeed when I submit the pref page, en event is triggers on the server side... in the other page !

I hope these "incompatibilities" will be solved in the near future, all of this reduces the interest of using icefaces to develop portlet based applications.

Thanks a lot, I'll check this and let you know if I could solve my problem.

Hi,

I've got to edit and save portlet preferences in liferay; I'm using icefaces 1.8; My portlet class' processAction method is never called, although I create the actionUrl using the specific tag "portlet:actionUrl" and use it to post my form.

I can't make it work, do you have any example showing how to trigger an action in my portlet ? I can't believe it's not possible, the JSR 168 spec is quite clear about that...

Thanks in advance !

can't believe it ! The problem was probably too simple for my tortured brain :-)... I used the path "../css/cssLayout.css", now it seems that the css file could not be found, and that's it ! I changed to "/css/cssLayout.css" (as in your example, thanks Markus !), and my CSS is now OK !

by the way I've just downloaded firebug, the all-in-one client side debugger, and I wonder how I've always been able to work without it...

Thanks Markus, you gave me the right direction to solve my problem !

one thing to note: the firefox message in the console talking about the css having mime type "text/html" instead of "text/css" actually means the css could not be found !

Yes, I'm using the bundle liferay 5.1.2 / Tomcat 6.
It seems to me that the CSS is found, the problems is that Tomcat (?) returns the CSS with the mime type "text/html" instead of "text/css", as required.
At least it's what firefox logs in the console...

Thanks Marcus, I will try this ASAP, this work around should be sufficient for the moment. The point is, I'd like to avoid being tightly bound to Liferay. I think a solution must exist somewhere, either in Tomcat or in another server.

I'll post it when I find the solution...

I'm facing a problem using my own stylesheets in my JSF pages.
config: liferay 5.1.2, icefaces 1.8.0_6RC1, Tomcat 6

I have a template facelet and a simple basic template client which uses 2 css files of my own. When the portlet is displayed, my CSS files are not loaded because Tomcat returns the CSS file with mime-type set to text/html instead of text/css; I can see the error in the firefox error console. Tomcat is parameterized correctly regarding the mime-types.
As my CSS are used inside a portlet their URL is changed by liferay and look like "http://localhost:8080/c/guest/3", but I'm sure the errors are related to my CSS because when I remove the link to them the errors disappear...

I tried using several tags to reference my CSS, including "<ice:outputstyle...", "<h:link..." , I even tried to use the "/xmlhttp/" servlet-mapping in case the icefaces API would be able to deliver my precious stylesheets correctly.

Now I'm blocked, dunno how I can do to use my CSS... Any idea ??? or a sample close to my use case (portlet, icefaces, facelet template, and CSS ?) ? is it possible an issue in the icefaces 1.8 could explain that ?

thanks for help !

I'm currently working on exactly the same configuration, except that I'm using Tomcat based bundle. This sample works fine on Tomcat 6 / liferay 5.1.2; I encountered strange problems in the past with glassfish, my conclusion was that probably Glassfish was not as stable as required, although I can't be sure for this.
Anyway, deploying several portlets in liferay starting from the same netbeans project is not an issue, it should work. I saw no problem in your files; The one thing I notice is that your portlet has been deplyed, but is bogus (otherwise you'd not have the unavailability message). As a conclusion you must have the solution in your log files, it should be quite easy to solve based upon the exception.
Let me know what you see in the logs... And welcome to the world of portals and portlets !