publicContextPath

Version 1 by Mircea Toma
on Aug 26, 2013 12:05.


 
compared with
Current by Mircea Toma
on Aug 26, 2013 12:11.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 4 changes. View first change.

 |Name:|org.icefaces.connectionLostRedirectURI|
 |Values:|*null*\|valid URI to redirect page|
  |Name:|org.icefaces.publicContextPath|
 |Values:|*null*\|valid path|
 |Since:|2.0|
 |Scope:|application|
  
 h5. Application Scope
  
Setting _org.icefaces.connectionLostRedirectURI_ to a valid URI tells ICEfaces that when the Ajax Push connection is lost, that the client is to be redirected to the specified page.
  Setting _org.icefaces.publicContextPath_ to a valid path tells ICEfaces to replace the natural context path (usually, the web-application name) of all resources, form URLs, local bookmarks and local redirects to the specified path. This is useful when the application is served publicly through a reverse proxy or load balancer and one wants to avoid defining complex URL rewriting rules.
  
 {panel}
 {code:xml|borderStyle=dashed}
  <context-param>
<param-name>org.icefaces.connectionLostRedirectURI</param-name>
  <param-value>/myPath/theConnectionLostPage.jsf</param-value>
   <param-name>org.icefaces.publicContextPath</param-name>
  <param-value>/myPublicPath</param-value>
  </context-param>
 {code}
 {panel}
  
 {note:title=Compatibility}This context parameter only applies if you are using the compatibility component suite.{note}

© Copyright 2018 ICEsoft Technologies Canada Corp.