Messages posted by "deryk.sinotte"

Re:Is it possible read/write cookie with Icefaces 1.8.2.GA_P03 + Liferay-6.0.12?

deryk.sinotte — GMT

Looks to be a bug. I've created a JIRA: http://jira.icesoft.org/browse/ICE-8135 From what I can tell it's only the initial request where the cookie map is not properly populated. Subsequent requests do show the cookie map with relevant values.

Re:ICEpush 3.0.1 causes no response in JBoss 7.1.1

deryk.sinotte — GMT

A couple of things: 1) I don't believe you need to add the following to your web.xml: Code:

 
    icepush 
    org.icepush.servlet.ICEpushServlet 
    1 
 

 
    icepush 
    *.icepush

Those settings are only necessary if you are trying to use ICEpush in a Java EE environment without JSF+ICEfaces. It should be possible to simply include icepush.jar in your app and deploy it. Of course depending on the scope, scalability, etc of your project, moving to Enterprise Push Server might be worth considering at some point. 2) If removing the settings doesn't help, can you deploy one of our sample apps (like showcase) as part of your .ear and see if that has the same problem?

Re:PortableRenderer.rerender(GROUP) not working after Browser Window Refresh (F5)

deryk.sinotte — GMT

I've attempted to update and enhance our Wiki docs in this area so that the ways to use the APIs and why is a bit clearer: http://wiki.icesoft.org/display/ICE/Ajax+Push+-+APIs Thank for using ICEfaces and if you have an other suggestions or comments, please let us know.

Re:PortableRenderer.rerender(GROUP) not working after Browser Window Refresh (F5)

deryk.sinotte — GMT

Adding the individual views via ViewScoped beans should work. You just need to ensure that the reference to the renderer and the view being added are the appropriate ones for the current context. Normally we'd recommend getting a reference to the renderer in the bean constructor to be sure.

Re:PortableRenderer.rerender(GROUP) not working after Browser Window Refresh (F5)

deryk.sinotte — GMT

Instead of: Code:

 PushRenderer.addCurrentView(...

try Code:

 PushRenderer.addCurrentSession(...

You're likely get a new View on reload.

Re:Capture disconnection on the server

deryk.sinotte — GMT

Can you provide more information on your environment?

What version of ICEfaces?

What app server you are using?

Does your application use Ajax Push? Typically a "Network Connection Interrupted" (NCI) occurs when either:

a request takes too long to return (perhaps there is a long running task that doesn't complete in a timely manner)

an Ajax Push connection can't reliably make a connection to the server after trying a configurable number of times (if you are not using Ajax Push, you can turn it off)

Re:BUG: icefaces 3.0.1 no Gzip Compression

deryk.sinotte — GMT

If you are running with Mojarra, try using the following context parameter:

com.sun.faces.compressableMimeTypes

text/*

You can set the value to the content types you would like to have compressed. Note that if you set the project stage to development:

javax.faces.PROJECT_STAGE

Development

no compression will be applied.

Re:Is Ice push getPortableRenderer() broken in latest 3.0.1

deryk.sinotte — GMT

The initial reference to the PortableRenderer must be retrieved from a JSF request thread (ie has a valid FacesContext). So for example, during the construction of your Window-scoped bean. After that, the PortableRenderer reference can be used on non-JSF threads.

Re:ace:fileEntry Component not working with Liferay 6.1

deryk.sinotte — GMT

Yes, there used to be a YUI conflict but it should be gone in 3.x. Glad you got it going.

Re:ace:fileEntry Component not working with Liferay 6.1

deryk.sinotte — GMT

Odd...you shouldn't be getting redirected. Those updates that are coming back are basically responses to Ajax requests that should be handled by the JavaScript supplied by JSF and/or ICEfaces. Have you tried running the samples/showcase/showcase-portlets sample application? An example of the ace:fileEntry component is in there and should run fine. That might help narrow things down (e.g. an interaction with the tabs). Which browser are you using? If you try Chrome or Firefox + Firebug, does the client console show any errors trying to load/run JavaScript files? Perhaps a needed resource is not being loaded.

Re:Migrated IceFaces webapp to Liferay's Portlet loose Hibernate session

deryk.sinotte — GMT

I haven't tried to make it work with a portlet filter and we don't have any samples or docs around Hibernate. Googling for Hibernate with PortletFilter and I found: https://forum.hibernate.org/viewtopic.php?t=979240 Maybe that will help.

Re:Migrated IceFaces webapp to Liferay's Portlet loose Hibernate session

deryk.sinotte — GMT

Can it be made to work as a PortletFilter rather than a regular web app Filter?

Re:Migrated IceFaces webapp to Liferay's Portlet loose Hibernate session

deryk.sinotte — GMT

I'm not a Hibernate expert but portlets have slightly different notions of "session" than regular web applications. If I had to guess, I'd say it might be related to that and doesn't really involve ICEfaces. I recommend Googling for something like: Code:

hibernate "failed to lazily initialize a collection" portlet

That particular error seems to be pretty common and there are other people out there who have seen the same issue and been able to fix it. One of the top hits I got was: https://forum.hibernate.org/viewtopic.php?f=1&t=1002633 That forum might have more details for you.

Re:ICEFaces 2.0 and Liferay 6.0 Session Timeout

deryk.sinotte — GMT

I'll probably need a simple test case that shows the problem if that's possible. If not, perhaps the entire client-side console log from Firebug or Chrome console that shows all the communication between client and server up until the error dialog pops up.

Re:dataPaginator FAILS to work in IE inside portlet, works fine in Firefox and Chrome

deryk.sinotte — GMT

We'll probably need a bit more information here: What specific versions of ICEfaces, WebSphere Portal, and IE are involved? This sounds more client-side related so is there anything in the IE dev console in the way of logging or exceptions? Even Firebug or Chrome's console might be reporting some kind of problem but just dealing with it better than IE. If there is any relevant server-side logging, that would help as well. Please note that general support for WebSphere and WebSphere Portal is covered under our Enterprise Edition (EE) offerings. You can get more info here: http://www.icesoft.org/products/ICEfaces-EE/overview.jsf http://www.icesoft.org/projects/ICEfaces/supported-platforms.jsf