I'm wondering when/why I should use "org.icepush.contextPath" and how to make it work?
I have 3 Portlets in 3 .war-Files and they all use ICEPush. This leads to some errors and I figured it might be because they all try to use the same BlockConnection and lock each other out or something. Anyway I edited the "org.icepush.contextPath" context-param in each of the .war-Files web.xml and set it all to the same Path ( "MyPath" ). Now after redeploying my portlets I see a 404 Error in FireBug.
Am I on the wrong path if I want to unify the context-path my portlets use?
Ok, I thought that would be the case.
Another question (because of this I experimented with the contextPath): Is it possible to have like 2 .war-Files deployed to liferay and in each .war-File are a couple of portlets that use the PushRenderer?
So .war-File A has Portlets AA and AB. If something happens in AA it request a re-rendering of AB.
In .war-File B there are the Portlets BA and BB and if something happens in BA it re-renders BB.
Is this possible? Are there some kind of tricks to it? Cause I have 3 .war-Files and if I try to fire the PushRenderer nothing happens (though I use the PortableRenderer, but that shouldn't make a difference, or should it?)
The main purpose of the PortableRenderer is to be able to do push from a thread that's not a JSF request thread. For example, if you have some external source (JMS for example) that is triggering updates, the threads for those updates are not JSF threads (so no FacesContext). The PortableRenderer should be used in those cases. If all of your renders are triggered from JSF threads, the PushRenderer should work for the scenarios you describe.
Yeah I know where to use the PortableRenderer, I just use it cause my actual case is a bit different and I can't gurantee a FacesContext if I want to re-render. Just wanted to know if it is possible at all to have two webapps that both use the ICEpush Features. You said it should work, thanks for that info. Hopefuly I can get it to work.