Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 1.6
-
Fix Version/s: 1.6.2
-
Component/s: Tool Integrations
-
Labels:None
-
Environment:any
-
Support Case References:support case: #4204
Description
The same configuration works in a standard JSF environment.
-
Hide
- ICEfacesAcegiExample.war
- 6.79 MB
- Michael Thiem
-
- META-INF/MANIFEST.MF 0.0 kB
- WEB-INF/applicationContext.xml 7 kB
- WEB-INF/classes/.../messages.properties 21 kB
- WEB-INF/classes/.../messages_en.properties 19 kB
- WEB-INF/.../messages_en_US.properties 19 kB
- WEB-INF/classes/test/Bean.class 1 kB
- WEB-INF/classes/.../LoginProxyBean.class 2 kB
- WEB-INF/.../NoCachePhaseListener.class 1 kB
- WEB-INF/classes/.../NodeUserObject.class 4 kB
- WEB-INF/classes/test/StyleBean.class 2 kB
- WEB-INF/classes/test/TreeBean.class 6 kB
- WEB-INF/faces-config.xml 1 kB
- WEB-INF/html_basic.tld 244 kB
- WEB-INF/jsf_core.tld 25 kB
- WEB-INF/lib/acegi-security-1.0.1.jar 434 kB
- WEB-INF/lib/aopalliance.jar 4 kB
- WEB-INF/lib/aspectjrt.jar 112 kB
- WEB-INF/lib/backport-util-concurrent.jar 343 kB
- WEB-INF/lib/commons-beanutils.jar 100 kB
- WEB-INF/lib/commons-collections.jar 164 kB
- WEB-INF/lib/commons-digester.jar 96 kB
- WEB-INF/lib/commons-el.jar 110 kB
- WEB-INF/lib/commons-fileupload.jar 52 kB
- WEB-INF/lib/commons-lang.jar 203 kB
- WEB-INF/lib/commons-logging.jar 27 kB
- WEB-INF/lib/ehcache-1.2.3.jar 203 kB
- WEB-INF/lib/el-ri.jar 97 kB
- WEB-INF/lib/icefaces-comps.jar 624 kB
- WEB-INF/lib/icefaces-facelets.jar 574 kB
- WEB-INF/lib/icefaces.jar 658 kB
-
Hide
- ICEfacesAcegiExample-src.zip
- 110 kB
- Michael Thiem
-
- ICEfacesAcegiExample/src/test/Bean.java 0.3 kB
- ICEfacesAcegiExample/.../LoginProxyBean.java 1 kB
- ICEfacesAcegiExample/.../NoCachePhaseListener.java 0.9 kB
- ICEfacesAcegiExample/.../NodeUserObject.java 6 kB
- ICEfacesAcegiExample/src/.../StyleBean.java 5 kB
- ICEfacesAcegiExample/src/.../TreeBean.java 11 kB
- ICEfacesAcegiExample/src/.../all-wcprops 0.7 kB
- ICEfacesAcegiExample/src/.../.svn/entries 0.7 kB
- ICEfacesAcegiExample/src/com/.../.svn/format 0.0 kB
- ICEfacesAcegiExample/.../messages.properties.svn-base 21 kB
- ICEfacesAcegiExample/.../messages_en.properties.svn-base 19 kB
- ICEfacesAcegiExample/.../messages_en_US.properties.svn-base 19 kB
- ICEfacesAcegiExample/.../messages.properties 21 kB
- ICEfacesAcegiExample/.../messages_en.properties 19 kB
- ICEfacesAcegiExample/.../messages_en_US.properties 19 kB
- ICEfacesAcegiExample/.../messages_en_US.properties 19 kB
- ICEfacesAcegiExample/.../messages_en.properties 19 kB
- ICEfacesAcegiExample/.../messages.properties 21 kB
- ICEfacesAcegiExample/.../TreeBean.class 6 kB
- ICEfacesAcegiExample/.../StyleBean.class 2 kB
- ICEfacesAcegiExample/.../NodeUserObject.class 4 kB
- ICEfacesAcegiExample/.../NoCachePhaseListener.class 1 kB
- ICEfacesAcegiExample/.../LoginProxyBean.class 2 kB
- ICEfacesAcegiExample/WebRoot/.../Bean.class 1 kB
- ICEfacesAcegiExample/WebRoot/.../web.xml 4 kB
- ICEfacesAcegiExample/.../faces-config.xml 1 kB
- ICEfacesAcegiExample/.../.faces-config.mex 0.1 kB
- ICEfacesAcegiExample/.../html_basic.tld 244 kB
- ICEfacesAcegiExample/.../jsf_core.tld 25 kB
- ICEfacesAcegiExample/.../applicationContext.xml 7 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The problem is the channelProcessingFilter. If this filter is active (listed in the filterChainProxy) then icefaces does not work.
The icefaces acegi example does not contain this filter. Maybe this is a known problem.
However, switching from a non-secure to a secure channel is a fundamental requirement of a secure application.
Specifically, it seems that using the filterChainProxy causes the AJAX Bridge to throw an uncaught exception in synchronizer.js line 39:
if (window.frames[0].location.hash.length > 0) this.reload();
"uncaught exception: Permission denied to get property Location.hash"
It looks like the installed ACEGI servlet filters are blocking the requests for the Javascript files and redirect them to the context root path (/ICEfacesAcegiExample).
The components contained in the login page are not working because they rely on the Bridge being available and running.
One solution to the problem would be to not filter the requests made for /block/* and /xmlhttp/* paths (or maybe filter just on *.iface since the servlet pattern matching is not very powerful).
A second solution would be to not use Icefaces components in the login page. Once logged in the requests for the Javascript files won't be redirected anymore.
example application tested on tomcat 6.0