Messages posted by: evgheni.sadovoi  XML
Profile for evgheni.sadovoi -> Messages posted by evgheni.sadovoi [95] Go to Page: 1, 2, 3, 4, 5, 6, 7 Next 
Author Message
Do you have a simple sample which can show your problem?

A quick test of our ICEfaces 1.8.2 showcase available over here:


does not expose any problems in IE 10 with mentioned components.


If think in your case it would be better in your case to un-reder dataTable upon row selection and show selected data to the user instead of it. You can also provide an undo button which will clear previous selection and return datatable back to the interface.

One more thing:
Take a look at our ACE datatable examples in the ICEfaces 3 showcase over here:

Once there click on Row State or Row Selector Examples for hints on how to use RowStateMap in order to disable/enable row selection in the table via server side logic.

JIRA link:


Thanks again for reporting this. We will look into it.
Thank you for reporting this. This looks like a bug to me. I will create a JIRA to address this issue.
Yes JS is usually the way to go.

On the other hand this is how we'd implemented session expiry pop ups in ICEfaces:


If you have ICEpush JAR present in the classpath of your application it will be used to generate that Session Expiry dialog window with reload button.
This is not the first time I'm stating this, but anyway...

HTTP protocol is stateless. Therefore there is no connection between server and client after request/response phase. Therefore you will need to constitute another request to the server in order to find out the state of the session held on server. There is no way around this.

How other sites does that?

A: JavaScript (99%)

Good examples:

via JQuery:

via standard JS:

var timeOut = 1000 * 60 * 30; // 30 minutes
 var lastActivity = new Date().getTime();
 var checkTimeout;
 checkTimeOut = function(){
     if(new Date().getTime() > lastActivity + timeOut){
         // redirect to timeout page
         window.setTimeout(checkTimeOut, 1000); // check once per second

ICE-8907 has been resolved as of Jan 24th 2013.
I have a feeling that this problem is somehow related to the web.xml configuration.
As far as I can see our samples declare servlet 2.3 in the deployment descriptor. Can you try to replace it with a valid servlet 2.5 web.xml declaration?

Can you also provide your weblogic.xml file ?

It looks like your issue is related to the page update during navigation. Which is causing ace:dateTimeEntry JavaScript not to work as intended.

Can you try the following workarounds and let me know if they will work for you?

Option #1: Use redirect when navigating between pages. Either in your faces-config.xml navigation rules or by adding the following to your destination page URL: ?faces-redirect=true

Option#2: Put everything on the page within a panelGroup that is itself an immediate child of the body


 <h:panelGroup id="myID">
 //... your page content with ace:dateTimeEntry component(s)
Yes according to JIRA - PUSH-171 is not yet resolved. Therefore <async-supported>true</async-supported> parameter will not work with our latest ICEfaces release on Glassfish 3.1.2

I will try to find our more information in regards to PUSH-171 and post it here.

We apologize for the miss-communication in our release notes. We will correct them as soon as possible.

Best regards,
Evgheni S.

Thanks a lot for the detailed description.

I was able to reproduce your issue with ICEfaces 3.2 & a simple page like this:

<h:form id="iceForm">

<ice:commandLink actionListener="#{testBean.doSomething}">
<f:param name="moduleEntityId" value="{testBean.entityId}"/>


However running the same sample with our latest revision of code from SVN does not show this problem.

It would be very useful if you can send us all offending pieces of the code from your application that you'd discovered during your investigation so I can test them with our latest build locally.

Thanks again for your feedback!

Upload test...
If you see the attachment forum upload is working correctly
I believe we did not upgraded plugin for NB 7.1.2 yet and that might be causing an issue on your side. Try NB 7.1.1 instead.
This is a bug described over here: http://jira.icesoft.org/browse/ICE-8240. It has been fixed. You can expect it to work correctly in the following versions of ICEfaces: 3.2 open source, EE-3.0.0 P01.
Profile for evgheni.sadovoi -> Messages posted by evgheni.sadovoi [95] Go to Page: 1, 2, 3, 4, 5, 6, 7 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team