ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

After playing with it, i realize it is not the Liferay.Popup that breaks IceFaces portlets, but the way to put the content in it that is widely use for other type of portlets..

I have come up with a very feasible workaround and can use Liferay.Popup in combination with IceFaces portlet and a very small customization to my Liferay theme...

For details see: http://www.liferay.com/community/forums/-/message_boards/message/4520197

Hope that helps someone...

The services work with any type of portlet.... The services, can be developed in a plugin or in EXT...

When developed in EXT they are available to any portlet (all porltets)...

When developed in a plugin they are available to portlets developed in the same plugin.

In either case they are usable by portlets developed in plain JSP, struts, Faces, or any other available framework.

All the portlets we/ve created are in 1.8.2 in Liferay 5.1.2 running on tomcat 5... They work fine... Perhaps give mover info?

If you have databases in Liferay, you surely used the Services layout, right? using service.xml?

If so, did you add methods to read/write data in your *LocalServiceImpl file?

If so, all you need to do from your backing beans is gather the data and call your

WhateverLocalServiceUtil.addData(myTableDataModel);

Hope that makes sense.

This is probably obvious. But an IceFaces portlet placed normally in a Liferay layout has something like this:

Code:

 <script type="text/javascript">try { document.execCommand('BackgroundImageCache', false, true); } catch(e) {}</script></div><script id="-sqOcSxJuwUERUA6bE7HXg:7:configuration-script" type="text/javascript">window.disposeViewsURI = '/MyPortlet/block/dispose-views';
 var [b]container[/b] = '-sqOcSxJuwUERUA6bE7HXg:7:configuration-script'.asElement().parentNode;
 container.[b]bridge[/b] = new Ice.Community.Application(..., container); ...

While the portlet that is shown via the popup is missing that...

Any clues as to how I could force the inclussion of that code?

Hi all! I'm using IceFaces 1.8.2 and LR 5.1.2...

I'm trying to use an IceFaces portlet that works great as a regular portlet in a liferay layout, but now inside of a liferay popup, using Liferay.Popup function. The function takes a portlet action url...

I can see the popup and the portlet in it, but then a show stopper... Nothing works in the portlet... Any action attempt results in:

Error: uncaught exception: couldn't find container for property: bridge

Any idea how to solve this issue?

Thanks in advance!

It has to do with the order in which the portlets are loaded, because if i move the one that requires asynchronous updates before the one that does not, both of them work fine...

Otherwise the one that requires asynchronous updates always has a red connection monitor icon and doesn't work at all... It works only if i maximize it which makes the other portlet not be loaded...

Hi all!

I have 2 portlets developed using 1.7 (latest sp). One of them uses file upload and a progress bar which requieres synchronousUpdate=false... The othe, in the other hand does not require it...

If i set synchronousUpdate to true on one and false on the other, the one portlet that requires asynchronous updates does not work (the connection status is red)...

Is this something that can be worked around or is that the way it is supposed to be?

Thanks in advance!

Hi All.

I'm using 1,7.2 ... I've constructed a facelets component that has a datatable in it, some text fields and a form to add data to the table...

When i use it outside of another datatable, the data table in my component behaves as expected, it refreshes if I add or remove data to the underlying model. Other components behave correctly as well (text fields with row count for example).

However, if i put the component inside of another datatable, the component's table does not refresh... The other components do refresh fine...

What can I do to correct this issue or to force the table to refresh?

Thanks!

Well, it is excellent to hear that is being addressed... The fix that reloads would be enough for now...

We'll eagerly await 1.8...

I really appreciate your reply!

I see now... I had not realized it could be used to prevent the dialog, but now i read the manual, and you are right...

Thanks a lot for pointing me in the right direction...

It's not clear to me how this will work with multiple portlets on the same page with the connection status... But i can try it...

Thanks!

I've searched the docs and forums and can't find an answer so far...

How can I override the look and content of the Session Expired Popup?

Thanks!

Hi all!

I'm not too surprised about this issue, as it kind of also happens with other faces frameworks that loose state if the user clicks the back button...

In my IceFaces usecase, I have portlet A and B on page 1, if i navigate to page 2 and use another instance of portlet A, use the back button to navigate back to page 1 and use portlet A (click on it), it works fine... However, if I click on bortlet B, I get the User Session Expired Popup... This is rather interesting...

I have a few questions: Is this expected behaviour? Will it be fixed or is there a workaround?

Ideally i would love for it to work w/o error... But if that's not possible, Is it possible to override the 'User Session Expired Popup' So that I can make it look differently and put different text on it, perhaps make it auto refresh?

Is there a way to override the Back Button usage?

Thanks in advace for your time and answers!

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.

i can't give you help in your particular problem.

What i can say is that yesterday i checked out Liferay from svn and my sample IceFaces portlet worked fine along with struts based and my faces based portlets... Hoping for a 4.3.1 soon!

I really hope all IceFaces components work too!