Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: 3.0.1, EE-3.0.0.GA
-
Component/s: Bridge
-
Labels:None
-
Environment:ICEFaces 3 + myfaces 2.1.6 + WebSphere 7 + Portlet
Description
On converting to Myfaces 2.1.6, the listen for push request wouldn't have the browserId cookie set, leading to the ConfigurationServer responding with a browserId, not as a cookie, but in the body of the response. The bridge wasn't picking up this value, leading to a tight loop where the next listen for push would trigger the cycle again.
Issue Links
- blocks
-
IPCK-259 Add ICEfaces EE Support for WebSphere Portal 7
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #27991 | Wed Feb 22 14:56:05 MST 2012 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces3/branches/icefaces-3.0.x-maintenance/icefaces/lib/icepush.jar
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #27990 | Wed Feb 22 14:49:01 MST 2012 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/lib/icepush.jar
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #27989 | Wed Feb 22 14:43:53 MST 2012 | mircea.toma | |
Files Changed | ||||
MODIFY
/icepush/trunk/icepush/core/src/main/javascript/application.js
|