Our current handling of ICEfaces IDs and view numbers causes problems when there are multiple ICEfaces portlets on a page served from separate archives. The problem stems from the fact that ICEfaces IDs and view numbers are not generated based on the session, which is shared between multiple portlets on a page. Instead, these framework specific IDs are generated per servlet, which are NOT shared between portlets when those portlets are served from separate deployment archives (war files).

So there are at least two things that probably need to be done:

1) The generation of ICEfaces IDs must be session specific. That is, portlets that may be deployed as separate web apps but could potentially share a session so the ICEfaces ID must be generated and stored in reference to that shared session to ensure that additional communication is properly directed.

2) View numbers generation needs to be unique to the session to avoid view number collisions in portlets served from separate deployment archives.