ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Hello,

In a table I have 2 cells per line which refer a panelTooltip (basically the cell contains a short description of an object and the tooltip a long description).
I have created a tag in my taglib in order to achieve this goal. The tag looks something like that

Code:

<f:view xmlns="http://www.w3.org/1999/xhtml"
 	xmlns:f="http://java.sun.com/jsf/core"
 	xmlns:h="http://java.sun.com/jsf/html"
 	xmlns:ui="http://java.sun.com/jsf/facelets"
 	xmlns:ice="http://www.icesoft.com/icefaces/component">
 
 	<!--
     Component responsible for the display of a BeanReference.
     PARAMETER:
         * "field" (mandatory) is the BeanRefeference to be displayed.
     -->
 
 	<f:subview id="ref_#{field.id}">
 		<ice:panelGroup panelTooltip="::refTooltip">
 			<ice:outputText value="#{field.value.shortDescription}" />
 		</ice:panelGroup>
 		<ice:panelTooltip id="refTooltip" hideOn="mouseout"
 			rendered="#{not empty field.value.longDescription}" hoverDelay="500">
 			<f:facet name="body">
 				<ice:panelGroup>
 					<ice:outputText value="#{field.value.longDescription}"/>
 					<ice:outputText value="#{field.id}"/>
 				</ice:panelGroup>
 			</f:facet>
 		</ice:panelTooltip>
 	</f:subview>
 	
 </f:view>

Unfortunately this does not work correctly, as my 2 cells point to the same tooltip. I tried generating an id for each "field" bean, but then I have an exception (IllegalArgumentException) in the UIComponentBase.validateId.
I have also tried using the "::id" technic but I'm not sure to fully understand it because I still have the same problem.

How am I supposed to proceed ? I'd like my first panelGroup to point to the next panelTooltip, and I think I must use the id for this...

Thanks !

Hello,

just a confirmation please... I guess the DND is not possible between portlets ? perhaps the DND only works if objects share a common JSF UIViewRoot... Am I right, or does anyone knows any means to achieve my DND between 2 portlets ?

Thanks !

Hello,

I'm setting up an IDE to allow a development team implementing modules of many types (a framework ==> several jars; a taglib containing some facelets of ou own; some business modules containing xhtml pages as well as classes; a parent project for all this stuff, to be packaged as a war and deployed to Liferay). These modules are coded in eclipse, projects are based on maven.

I think I'm not the only one to meet this kind of need ? does anyone have setup some maven archetypes for this kind of context ?

Thanks !

Thanks, I'll have a look.
Regards

I intend to use jquery scripting in my icefaces portlets (on Liferay) to make the stuff more "dynamic". Indeed I think that for ex a collapsible panel may be able to collapse / expand in the browser directly instead of being forced to refresh from the server. But there are lots and lots of interesting usages...

So I'm trying to build a sample portlet containaing a collapsible panel which will expand/collapse in the browser. I intend to publish it here when I'm done.

Anyone has already done this ? I'd be most interested to get the sources...
otherwise I'm interested in any advice: jquery requires the ids of the tags on which we intend to work but in a portal the ids are generated so I must be able to retrieve the generated ids, and for now I dunno how to.

Thanks to all and I'll post my results... If I achieve my goals !

hello,

I've been developping with icefaces in Liferay for several months now, but I'm quite new to developments which allow user editing data inside a table.

One of the requirements I have is that the user must show his intent to edit the table before being able to do so. So far I've been trying to create my table with attributes "disabled" in editable tags, set to true or false depending on the user choice. I'm not really satisfied, the table is not really pretty... So I wonder if it's the right way to do this or if I'd better create 2 *.xhtml, the first for the simple display of the table, the second one being displayed when the user edits it (using stacking panel).

how do you proceed ?
Thanks

does anyone know if it's possible (and how) to define a popup menu which will be triggered by right click on any cell of a column, but which will be defined only once ?
I mean, I have no problem defining a popup menu in each cell of a column in my tables, but if I'm displaying 50 lines, the menu is included 50 times in my page...

Thanks.

hello,

I'm implementing an application which relies heavily on icefaces' IPCs facilities (inter portlets communications).
In a portlet, my jsf page allows the user selecting clients. When he validates, this selection is shared in the session and an ajax refresh is triggered. 2 other jsf views (in 2 portlets) are then notified, and rebuild their content starting from it.

I'd like the outputConnectionStatus to show a request is currently running in each portlet, starting from the moment when the ajax refresh is triggered on the server side... But actually it does not.

any idea anyone ? Thanks !

as far as I can I try not to use dataBindings, to me the GUI should call the beans, and not the opposite...
but if I can solve such blocking issues I can make some effort :-).
Thanks, I try this ASAP.

Hi all,

I have posted on some other threads but not this one it sesms.
This bogus behaviors disappeared with Tomcat. I have replaced Tomcat with Glassfish 2 (bundle Liferay 5.2.3 / Glassfish 2) and never saw it again !
To me it was something related to hot deployment in Tomcat... though I think I'll never have the whole explanation.

hello,

I have 2 portlets in a page, built on icefaces 1.8.2.
My portlets use 2 request-scoped managed-beans. These beans implement icefaces' DisposableBean interface, which means they should be automatically disposed by the framework when they expire.

When I drop a new portlet application into the page, my managed beans don't receive the dispose message, but new instances are created by the bean manager... that causes anomaly in my application as the bean state has not been saved before (the state is saved when the bean is disposed).

Is this a Liferay related issue or rather an Icefaces issue ?
Thanks !

OK Now I can export... almost nothing !
My table contains one <ice:column> to allow row selection, an <ice:columns> to specifiy the row's structure which is based on a bean implemented from an array of data (to be generic all my beans are implemented this way.

The trouble seems to be that only <ice:column> tag seems to be exported, isn't it ? I only get an excel file containins the values of my first column (true is the row is selected...).

I don't have headers (whitespace instead) nor do I have the values for my beans...

Is this normal or am I missing something ?

Thanks !

which version of Liferay are you using ? I can't see the "configuration" menu you're talking about. Do you mean the standard portlet buttons on the top-right of it ? If so you must modify the portlet.xml as the prefs (aka configuration data ?) is a concept which is defined by the jsr 168.

Just as you have
<init-param>
<name>com.icesoft.faces.portlet.viewPageURL</name>
<value>/xhtml/relationshipChooser.iface</value>
</init-param>

which allows you specify the 1st page of your portlet, you can add

<init-param>
<name>com.icesoft.faces.portlet.editPageURL</name>
<value>/xhtml/EditPreferences.iface</value>
</init-param>

to set the prefs edition page.

Personaly, for now, I've not implemented prefs management like this, I'm using a standard JSF page (chained to other pages using navigation configuration in faces-config). The trouble is the portlet and the pages it displays do not know each other, their states are separated and you'll face numerous issues to make them communicate efficiently...

Well, I think the only way to keep the header visible and to have the rest of the table scrolled is to use 2 tables, one for the header and one for the rest...
Thanks for the workaround, I'll try it. I have a ticket open for this issue, I hope it will be solved in a future release.

Thanks however

well your portlets belong to 2 different wars so they don't share anything except the fact they're hosted be the same portal. So I guess you ought to rely on it to share data.
I have tested this a few months ago, it works but you must be very careful to the classes you deploy as a portal extension because you may experience some class loading issues... Furthermore you must remember you are developping based on Liferay's architecture, any migration to another portal would imply to change this.

I remember I had found a post of Neil Griffin which explained the stuff. You have to use the class "portalclassinvoker" (from Liferay package).
http://www.liferay.com/web/neil.griffin/blog/-/blogs/sharing-data-between-portlets;jsessionid=E81EFC4FE3B06232970A2A8CF0982317

I'm interested in your experience, please post your opinion when you're done.