Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: EE-3.3.0.GA_P02, 4.0
-
Fix Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03
-
Component/s: Framework
-
Labels:None
-
Environment:Firefox, ICEpush
-
Assignee Priority:P2
-
Workaround Exists:Yes
-
Workaround Description:If not using push, remove the icepush.jar file.
Description
With lazyPush=true, the blocking connection shouldn't be active until the first push is requested. In Firefox this connection is active as soon as the page is accessed. There are calls to listen.icepush.xml.jsf showing in the browser and firebug consoles.
This isn't an issue with Chrome or IE11.
This isn't an issue with Chrome or IE11.
-
Hide
-
-
META-INF/MANIFEST.MF
-
META-INF/context.xml
-
WEB-INF/classes/com/.../support/Item.class
-
WEB-INF/classes/.../support/TestBean.class
-
WEB-INF/lib/icefaces-ace.jar
-
WEB-INF/lib/icefaces.jar
-
WEB-INF/lib/icepush.jar
-
WEB-INF/lib/javax.faces-2.2.7.jar
-
WEB-INF/web.xml
-
index.xhtml
-
welcomeICEfaces.xhtml
-
-
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I cannot reproduce this issue. I used Firefox 33.1. I didn't see the blocking connection initialized after loading the page. Tested both the trunk and 3.3 maintenance branch.
Show
Mircea Toma
added a comment - I cannot reproduce this issue. I used Firefox 33.1. I didn't see the blocking connection initialized after loading the page. Tested both the trunk and 3.3 maintenance branch.
Attached test case that shows the issue.
Steps:
- Load welcomeICEfaces.jsf in Firefox
- Monitor the browser/firebug console to see the listen.icepush.xml.jsf calls.
Show
Arran Mccullough
added a comment - Attached test case that shows the issue.
Steps:
Load welcomeICEfaces.jsf in Firefox
Monitor the browser/firebug console to see the listen.icepush.xml.jsf calls.
Tested with ICEfaces 4 trunk and ee-3.3.0 maintenance branch r43633. Tomcat 7, FF 33 and FF 34. Not able to reproduce issue.