voyent
Liferay portlets + ICEfaces powered portlet  XML
Forum Index -> Portals & Portlets
Author Message
corwin


Joined: 03/Aug/2007 00:00:00
Messages: 2
Offline


Hello, All!

I'm looking for AJAX JSF components working successfuly inside JSR-168 portal environment, especially inside Liferay Portal. I'm try ICEfaces sample from Liferay site and my custom portlet developed with ICEfaces and have the same results: ICEfaces raise JS error "connection not exists" if ICEfaces powered portlet add to page which already contains Liferay portlets. In the same time ICEfaces portlet successfuly work inside Liferay if portlet add to page has no portlets.
It seems no way for use ICEfaces powered JSF portlet on the same page with Liferay standard portlets.
In view of above I have two questions:
1. Does ICEfaces team plan to improve component and portal collaboration?
2. Anyone success in use ICEfaces and Liferay standard portlet on the same page inside Liferay Portal?

Regards!
Anton Naumov
Telpochyaotl

Joined: 23/Apr/2007 00:00:00
Messages: 21
Offline


I have not tested thoroughly, but the issue you report seems only present in 4.3.0 of liferay... I did a quick test and stuff seemed to work fine with liferay code from the trunk, so either try the trunk or wait for a 4.3.1 hopefully soon.
deryk.sinotte


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


To answer your questions:

1) We are definitely working to improve our portal support. Not only with Liferay but other portal implementations as well. There are a number of technical issues that make it challenging to support ICEfaces portlets on a page and when you add in portlets using other technologies, the issues can grow exponentially. Typically the problem is related to JavaScript (either collisions of some kind or mismatched library versions). We are doing are best to work through these but the matrix of possibilities gets very large very fast.

2) Could you tell me which non-ICEfaces Liferay portlet(s) you are trying to use on the same page as the ICEfaces portlet? It would help to narrow things down.

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
corwin


Joined: 03/Aug/2007 00:00:00
Messages: 2
Offline


First of all thanks for quick and usefull answers.

2deryk.sinotte,
1) I'm understod it's huge job to support different portals compability and I don't wait a full error free work of ICEfaces inside portals very soon. May be if Liferay guys migrate portal presentation to JSF (it was announcement for Owen, but it seems thay suspend or discard this migration) and may be they use ICEfaces as main library for this work :). However, I'm looking for working AJAX JSF library in portal environemnt. It means, the JSF library usage may produce some customization and/or improvement inside different portal implementation, but it should work. I mean first of all send AJAX requests and receive AJAX responses inside JSF portlet. And of course it should work in collaboration with other portlet, otherwise it's no sence to use JSF portlets.
2) I'm trying sample ICEfaces porltet available on Liferay site as example of ICEfaces integration. And I have JS error each time when I'm trying to fill properly fields in ICEfaces portlet added to Guest -> Home Liferay page. By deafult it contains Sing In portlet and Journal Content portlet, both portlet rendering through AJAX, so it seems the JS libraries conflict. May it would be reasonable make JS prototype library turn on/off inside ICEfaces for aviod problems with already defined prototype?

Regards!
Anton Naumov
deryk.sinotte


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


ICEfaces portlets do work proprerly in Liferay with other ICEfaces portlets on the same page. The challenge is to work with other non-ICEfaces technologies. This is, of course, desirable but the sheer number of other technologies that you can potentially include on a portal page makes it difficult to ensure we cover them all. I think you'll find that other AJAX frameworks are also encountering the same issues.

I know Liferay is interested in adding ICEfaces to some of their existing portlets but I can't comment on which ones or when that might happen.

We can't really turn off the prototype/script.aculo.us library as it is an integral part of our AJAX bridge on the client. While this could change in the future, it's a reality for the moment.

I'll add the Sign-on and Journal Content portlets to our list of portlets that the community would like to see working. As a company that develops an open source product and relies on services and support to generate revenue, we are driven by the demands of the community and our paying customers. You can probably guess how things get prioritized ;-)


Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
 
Forum Index -> Portals & Portlets
Go to:   
Powered by JForum 2.1.7ice © JForum Team