ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

There is a problem I have using a scrollable dataTable depending on the rime theme.
The left outer line of the whole table has 1px distance too much from the table and is too long, too. The rest is ok.
Switching back the dataTable to not be scrollable I do not have this problem.
A screenshot is attached ...
I tried a lot of stylesheet adjustments, but none of them worked ...
How can this be fixed?

Hello Ken,

perhaps this issue is also related to a javascript error coming up in IE8 only on every interaction with a page (e.g. button gets pressed). Normally you don't see it, but I switched on the option "Display a notification about every script error" in the advanced settings of IE8. I've attached a screenshot of this error.
Can you say when the version 2.0.1 gets released?
For now I have to go back at first to version 1.8.2 there the memory leak problem does not exist.

Thank you very much for your investigation,
Uwe

I've found an old bug entry with the same issue with ICEfaces version 1.7.2 and IE6:

http://jira.icefaces.org/browse/ICE-3423

Seems like it's the same now with version 2.0.0 and IE8 ...

I can see the iexplore.exe in the task manager increasing every time I show a panel popup. Deploying the component-showcase.war (ICEfaces 2 version) has the same behaviour. The component showcase online I think is still running with version 1.8.2 there I can not see any memory leaks.

Here's an example of the code, I think there's nothing special to it:
Code:

 <html xmlns="http://www.w3.org/1999/xhtml"
   xmlns:h="http://java.sun.com/jsf/html"
   xmlns:f="http://java.sun.com/jsf/core"
   xmlns:c="http://java.sun.com/jsp/jstl/core"
   xmlns:ice="http://www.icesoft.com/icefaces/component"
   xmlns:icecore="http://www.icefaces.org/icefaces/core"
   xmlns:ace="http://www.icefaces.org/icefaces/components"
   xmlns:ui="http://java.sun.com/jsf/facelets"
   xmlns:nkg="http://www.siemens.com/nkg/components">
 <ui:composition>
   <ice:panelPopup modal="true" draggable="false"
     visible="#{value.visible}" autoCentre="true">
     <f:facet name="header">
       <ice:panelGroup>
         <ice:outputText value="#{value.title}" />
       </ice:panelGroup>
     </f:facet>
     <f:facet name="body">
       <ice:panelBorder>
         <f:facet name="center">
           <ice:panelGroup>
             <ice:outputText value="#{value.message}" />
           </ice:panelGroup>
         </f:facet>
         <f:facet name="south">
           <ice:panelGroup>
             <ice:commandButton value="#{i18n.button_ok_text}"
               styleClass="iceCmdBtn" actionListener="#{value.confirm}" />
           </ice:panelGroup>
         </f:facet>
       </ice:panelBorder>
     </f:facet>
   </ice:panelPopup>
 </ui:composition>
 </html>

I include this xhtml into my main page (tag library):
Code:

 <nkg:messagePopup value="#{inductionsBean.messagePopup}" />

While testing my ICEfaces 2 application I've regognized that after each modal popup open and close the memory of the IE increases by around 10 Mb! I did not have this problem with the ICEfaces version 1.8.2. Is this a known behaviour and is there a solution for this?
I also deployed the ICEfaces 2 component-showcase war in my application server and there had the same memory leak problem while testing the modal popup.

Here's my test setup:
IE8
Windows 7 / Windows XP
ICEfaces 2.0.0
JBoss AS 6.0.0

I also tested the modal popups with Safari and Firefox, they did not have any memory leaks.

Thank you very much for your response.

While testing my ICEfaces 2 application I've regognized that after each modal popup open and close the memory of the IE increases by around 10 Mb! I did not have this problem with the ICEfaces version 1.8.2. Is this a known behaviour and is there a solution for this?
I also deployed the ICEfaces 2 component-showcase war in my application server and there had the same memory leak problem while testing the modal popup.

Here's my test setup:
IE8
Windows 7 / Windows XP
ICEfaces 2.0.0
JBoss AS 6.0.0

I also tested the modal popups with Safari and Firefox, they did not have any memory leaks.

Thank you very much for your response.

I've found the problem causing the session expire problem. As soon as a call my own servlet in order to generate the report pdf stream I get the HttpSession via the HttpServletRequest object (input parameter of the doGet method). -> I do not get my existing session but a new session and anyhow the framework doesn't like that and I get the user session expire popup. If I do not try to get the session everthing works alright, but the problem is I need it.

So the new plan is to just create a JSP page that holds the same code (functionality) like the servlet class. There the session object is already known and I assume it is the same session of the dialog that is running at this time. Should perhaps work without getting the session expiration.

I also tried to touch the session and use a phase listener but this can not work because the new session that is created by the servlet is not known by the ICEfaces lifecycle.

no, I took the all configuration. Just made a copy and renamed it ...

Because it will not change the result. I still have that session expire problem. What I now tried was to touch the session in my report servlet. But anyhow the SessionDispatcher cannot be resolved at runtime. It ist located in the icefaces.jar that is deployed in my JBoss. Can anyone help?

Well, actually I'm not using Seam. I posted it here because of my integration of ICEfaces into JBoss. I simply created a JBoss configuration, added all dependency ICEfaces and Jasper libs and deployed my EAR. It's running good, except that session expiration with that modal dialog.

Hello,
my setup is JBoss 5.0.1, ICEfaces 1.8.2 and JasperReports 3.7.2.
In all of my jspx Dialogs I have a button for generating a jasper report. Pressing it opens a modal ice popup. This popup includes an iframe with a fix size. The target url of the iframe gets set dynamically via a javascript call after the button has been pressed. The target url of the iframe calls my own report servlet (extending HttpServlet) that generates a pdf and streams it back into the iframe. The user than can print or save the pdf or close the modal report popup again.
Now the problem is as soon as the user closes the report popup i get a session expire message from icefaces and must reload my origin dialog again.
Did anyone have the same problem or a similar yet or has any solution for this behaviour?

Here's a few code snippets ...

javascript call:
Code:

 JavascriptContext.addJavascriptCall(this.context, "document.getElementById(\"reportPrintIFrame\").src = \""
           + servletURL + "\";");

report servlet declaration:
Code:

 public class JBReportServlet extends HttpServlet

web.xml extraction:
Code:

   <context-param>
     <description>To allow multiple windows for a single application.</description>
     <param-name>com.icesoft.faces.concurrentDOMViews</param-name>
     <param-value>false</param-value>
   </context-param>
   <context-param>
     <description>Turn on/off application-wide synchronous or asynchronous updates.  </description>
     <param-name>com.icesoft.faces.synchronousUpdate</param-name>
     <param-value>false</param-value>
   </context-param>
   <servlet>
     <servlet-name>Report Servlet</servlet-name>
     <servlet-class>com.lsb.reporting.JBReportServlet</servlet-class>
     <load-on-startup>1</load-on-startup>
   </servlet>
   <servlet-mapping>
     <servlet-name>Report Servlet</servlet-name>
     <url-pattern>/reports</url-pattern>
   </servlet-mapping>

Hello,

I'm using icefaces 1.2.7 SP1. I have a data paginator for my data table. It is bound to my bean and it has an actionListener onPaging. The onPaging method calls a submethod that calculates a sum of all visible datasets in the datatable. Now if a page to e.g. index 2 in my datatable (maxrows = 5) to see the next rows the row index of my bound data paginator object is still on the old value. Actually it should already carry the data for the next page ... So my sum is always wrong because I never know on which page I am actually. Do you have a solution for this?
Thanx, Uwe ... here's my code:

Code:

   public void onPaging(ActionEvent event) {
     this.calculateTotalNumberOfPieces();
   }
   
   private void calculateTotalNumberOfPieces() {
     this.totalNumberOfPieces = 0;
 
     int firstRowIndex = this.dataPaginator.getFirstRow();
     int lastRowIndex = firstRowIndex + this.dataPaginator.getRows();
 
     for (int i = firstRowIndex; i < lastRowIndex; i++) {
       this.totalNumberOfPieces += discharges.get(i).getNumberOfPieces();
     }
   }

Hi!
As soon as I create a datatable with multirows in the header and set the datatable to be resizable, it doesn't work anymore. The columns look strange and I can't resize the columns anymore. With only one header row it's working.
Any ideas, or is it a bug?
Thanx,
Uwe

After getting your local or remote EJB reference in the backing bean, if you imagine you start a transaction (EJB method call) from your backing bean, best is to let through all exceptions (especially runtime exceptions) and just catch them in the backing bean (when the transaction gets closed). If an error occurs now like e.g. a SQL exception the trancaction will get a rollback and you don't run into data inconsistency in the database.

Hi again,

I found it, it's explained in the icefaces component docs.
For anyone who has the same problem, here's a starting examle:

<ice:dataTable ..>
<f:facet name="header">
<ice:columnGroup>
<ice:headerRow>
<ice:column rowspan="2">
<ice:outputText value="First Name"/>
</ice:column>
<ice:column rowspan="2">
<ice:outputText value="Last Name"/>
</ice:column>
<ice:column colspan="2">
<ice:outputText value="Contact Info"/>
</ice:column>
</ice:headerRow>

<ice:headerRow>
<ice:column>
<ice:outputText value="Phone"/>
</ice:column>
<ice:column>
<ice:outputText value="Email"/>
</ice:column>

</ice:headerRow>
</ice:columnGroup>
</f:facet>
......
......
</ice:dataTable>