ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I did nothing with the liferay scripts. All on my own.

Could you post your portlet.xml, web.xml and packet structure? I'm trying to setup the same project structure you are using, but haven't managed to get it working.

- Erik

Hi Thierry - could you post your ear package structure? I'm trying to create a Liferay/Seam/ICEfaces/Facelets project on JBoss AS right now. Unfortunately, I'm stumbling around and not making too much progress.

If it's a war deployment you are looking for, there is a target for jboss/liferay in seam-comp-showcase that you could take a look at.

Thanks for the response, Judy. I'm still looking for an ear deployment because my current project is using the seam-gen generated ear structure, but a war deployment would suffice, too. I just wanted to keep my ear structure. I was also a bit concerned because my project uses jbpm - and I was concerned about the setup changes I would need to make. I'm thinking I would put the jbpm libs in the WEB-INF/lib directory, but I'm not too sure.

I'm also aiming for deployment to Liferay 5.2.3 - which is not listed in the readme.txt in the ICEfaces/Seam component showcase - so I'm not sure if Liferay 5.2.3 is supported. Argghh - this is the part of JEE dev that I hate the most - all the setup stuff. It would be nice if there was a ICEfaces/Seam gen to deploy to JBoss/Liferay, but probably too few people are using that configuration. But I'll give the war deployment a try, modify my Seam gen build.xml, and see what happens.

The issue with ear deployment is that the Liferay script that is used to deploy is for wars only (unless that has changed with newer releases, and you might want to check with Liferay about that). As for the newer versions of Liferay, just edit the portlet config files that are in the resources folder for that particular option in seam-comp-showcase to include the newer version (I haven't had any problems with this when new versions have come out). Let us know if you have any problems, but if you are not using the ejb3 container & it's features, it shouldn't be any problem at all to deploy your application in a war deployment.

Hi Judy,

I took a closer look at the seam component showcase and I noticed that it does not use Facelets. I've also read somewhere that the combination of Facelets/Seam/ICEfaces/Liferay does not work. Do you know if this is true?

Actually seam-comp-showcase only uses facelets. There is no jsp version.

If you could point out anywhere that you have read that Seam/ICEfaces/Liferay doesn't work, please send me the link so we can set them straight. We have had a target for this configuration in seam-comp-showcase for some time now.

In regards to the link, I can't remember where I found that. If I come across it again, I'll send it to you.

I've actually been able to make some progress on my war deployment. I'm moving my prototype to work as a portlet(s) in stages, but things have been surprisingly smooth so far. After making my setup changes, I was able to deploy a simple portlet in Liferay with the ICEfaces/Seam/Facelets configuration.

Here are the things (that I didn't expect to work or that I had concerns with) that are working so far:

EJB - stateful session beans

Seam application framework

Hibernate filters

Hibernate Search integration

*.page.xml and pages.xml

*.component.xml and components.xml

ICEfaces components such as popup, collapsible panel, etc.

Here are things that are not working (which may be limited by the Portlet spec):

Page parameters (at least retrieving them via the Seam @RequestParameter annotation or using them in the <param> tag in the *.page.xml file - it may work if I directly retrieving them from the ServletRequest)

Page actions - I was afraid this wouldn't work and it doesn't... I really wanted this to work. I wonder if there's a good workaround for this...

I have yet to try:

JBPM

Hibernate Validators

Again, I'm still surprised things have gone relatively smoothly given all the stories I've seen regarding Liferay/ICEfaces/Seam integration. :)

The Hibernate Validators will work (I have tried this). Might have to make some concessions regarding page parameters with jbpm since if you are using "GET" 's with page paramters, this requires a full page refresh (and look already at the URL when using portlets as it already contains a very different pattern than servlets so you have to limit to a single view application or you will get a redirect to a full new page which is out of the portlet that you were working on--hope this makes sense, but if you are working on it now, it should). Try to keep your portlets to a single page application and use facelets (ui:include rendered attribute mapped to boolean of backing bean for whichever fragment is currently being shown) to swap out fragments of your single page app. As long as your portlets isn't huge, this it manageable. Basically it is redirection with Seam within the portlet that is the only thing not available as normal Seam with Servlet.
Just some suggestions.

Oops, page actions do work. I'm not sure why it didn't work a few days ago - but yes, they do work.

Unfortunately, I'm still searching for a workaround for page parameters. I've been looking at implementing the FriendlyURL Mapper interface as detailed in:

http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/FriendlyURLMapper

But the wiki page isn't very helpful - so I'm not sure if FriendlyURLMapper will work as a workaround. Liferay documentation is just so sparse... and the forums aren't very helpful - no one seems to answer questions.

You can still use page parameters, it is just within redirection that it is a problem. I took the booking example and made a single view application (using facelets and seam)out of it. Instead of redirecting to a different view, the facelets were just shown as required with rendered attributes and page parameters were used with no problem. Would you really want redirection with full page refreshes with the portlet applications? (consider all the other portlets that would have to be re-rendered).

Yep, you are correct yet again. :)

I tried it again and page parameters do work (I wonder why it didn't work last time at all - I probably did something stupid like forget a converter) - with the limitation you pointed out in regards to redirects.

I guess I can use the rendered attributes technique, perhaps in combination with a stacking panel or another technique. Still not as elegant as separate pages - and it'll probably end up being a little harder to test things - but it will do for now. Thanks for all the great help Judy!

hi zzz,

i am struggling to deploy icefaces and seam portlet to liferay jboss bundle.if possible Can you please share portlet war file ?

Thanks