voyent
Messages posted by: jack.van.ooststroom  XML
Profile for jack.van.ooststroom -> Messages posted by jack.van.ooststroom [223] Go to Page: 1, 2, 3  ...  13, 14, 15 Next 
Author Message
Hello Fredrik,

Thank you for pointing this out. The fix to PUSH-381 should effectively avoid getting into the endless loop you described. When invoking org.icefaces.application.PortableRenderer.render(group) where the group argument is set to null it should now result in an IllegalArgumentException to be thrown.

Regards,
Hello Rohit,

Just to answer a few of your questions.

Only ICEfaces-EE is supported in cluster/fail-over environments.

ViewScoped beans reside in the session, thus in the case of a fail-over the session gets replicated, if configured correctly, including any ViewScoped beans as long as they are Serializable.

Are you using Push?

Regards,
Hello,

Have you tried to use Apache 2's mod_proxy_balancer instead of mod_jk?

Regards,
Hi,

I'm not sure what you mean by "to work with it". Once Tomcat 7 is configured correctly to use SSL, you can access your ICEfaces application either using HTTP (port 8080) or HTTPS (port 8443).

If you want to enforce HTTPS to be used when accessing your ICEfaces application, you can add the following to your web.xml:

Code:
 <security-constraint>
     <web-resource-collection>
         <url-pattern>/*</url-pattern>
     </web-resource-collection>
     <user-data-constraint>
         <transport-guarantee>CONFIDENTIAL</transport-guarantee>
     </user-data-constraint>
 </security-constraint>

I hope this helps.

Regards,
Can you try one of the stock sample applications shipped with ICEfaces 3.0.1, like auction, auctionMonitor or showcase?

I haven't been able to reproduce this using one of our stock sample applications on GlassFish Server 3.1.2. When building them please ensure to use the web-profile Ant target as it will result in the Mojarra libraries not being added to the resulting .war file.

Thanks,
I'd like to suggest using MyFaces 2.1.x on JBoss AS 5.x. The MyFaces libraries and its dependents can be included in the ICEfaces application's web archive. Additionally, add the following to the web.xml:
Code:
     <context-param>
         <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
         <param-value>true</param-value>
     </context-param>
Hope this helps.

Regards,
Hello,

What do you use to do the reverse proxying? Can you share the reverse proxy configuration with us?

Regards,
Hello,

It indeed looks like Tomcat 6 NIO is not supported by the AJP connector: Advanced IO and Tomcat. Tomcat 7 NIO does seem to be supported by the AJP connector: Connector Comparison

Please be advised that Push Server does not support Tomcat NIO. The Enterprise Push Server (EPS) does.

Regards,
In order to utilize Servlet 3.0's ARP ensure the following is done for the chat application:

  • Replace the web-app version in the web.xml from 2.5 to 3.0:
    Code:
     <web-app
             version="3.0"
             xmlns="http://java.sun.com/xml/ns/javaee"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

  • Add the async-supported element in the web.xml to the servlet declaration:
    Code:
         <servlet>
             <servlet-name>Faces Servlet</servlet-name>
             <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
             <load-on-startup>1</load-on-startup>
             <async-supported>true</async-supported>
         </servlet>

    Regards,
  • Hello,

    Can you post the web.xml of the application?

    Regards,
    ICEfaces 1.x is compatible with JSF 1.x
    ICEfaces 2.x is compatible with JSF 2.x

    ICEfaces 1.x will not work with JSF 2.x

    However, ICEfaces 1.x does support MyFaces based on JSF 1.x

    Regards,
    With the exception of the render.auto context parameter, I don't see anything out of the ordinary in the web.xml. However, I am unfamiliar with the current ICEfaces 2 and MyFaces 2 support, but JIRA ICE-5868 seems to indicate we still have some work to do. The current fix version/s is set to 2.1.

    Just as a sanity check, can you try your sample using the JSF libraries supplied in the ICEfaces-2.0.2 bundle and leave out Tomahawk?

    Thanks,
    As you only used the classes and the form of the easyAjaxPush sample tutorial, can you post the web.xml you're using here?

    Thanks,
    Hello Jonas,

    I tested with the render.auto set to false:

    Code:
     May 24, 2011 12:46:41 PM org.icefaces.util.EnvConfig init
     INFO: ICEfaces Configuration: 
     org.icefaces.render.auto: false
     org.icefaces.autoid: true [default]
     org.icefaces.aria.enabled: true [default]
     org.icefaces.blockUIOnSubmit: false [default]
     org.icefaces.compressDOM: false [default]
     org.icefaces.compressResources: true [default]
     org.icefaces.connectionLostRedirectURI: null [default]
     org.icefaces.deltaSubmit: false [default]
     org.icefaces.lazyPush: true [default]
     org.icefaces.sessionExpiredRedirectURI: null [default]
     org.icefaces.standardFormSerialization: false [default]
     org.icefaces.strictSessionTimeout: false [default]
     org.icefaces.windowScopeExpiration = 1000 [default]
     org.icefaces.mandatoryResourceConfiguration: null [default]
     org.icefaces.uniqueResourceURLs: true [default]
     org.icefaces.lazyWindowScope: true [default]
     org.icefaces.disableDefaultErrorPopups: false [default]
     

    However, by doing so, I don't see the other browsers being updated any more. The description of this context parameter seems to explain why this is:


    render.auto

    default is true

    Setting render.auto to true causes ICEfaces to automatically apply DOM rendering to each page. If this is set to false, then DOM rendering and updating is turned off for the entire application.

    <context-param>
    <param-name>org.icefaces.render.auto</param-name>
    <param-value>false</param-value>
    </context-param>

    This context parameter is application-wide and works together with the render attribute of the ICEfaces <icecore:config> tag so that ICEfaces rendering can be turned on and off selectively on a per page basis. To apply ICEfaces DOM rendering to select pages only, set this parameter to false and add:

    <icecore:config render="true">

    to just those pages that should be rendered via ICEfaces.
     

    But you're saying that even leaving this context parameter set to its default value you don't see the other browsers being updated anymore?

    You also seem to refer to JSF 2 (MyFaces implementation) and Tomahawk. Are you not using the stock easyAjaxPush tutorial sample?

    Regards,
    Hello Gilbert,

    Using ICEfaces-2.0.2-src and the easyAjaxPush tutorial source code from (http://wiki.icefaces.org/display/ICE/Easy+Ajax+Push) I was able to successfully deploy to Apache Tomcat 7.0.5 seeing the Server Push happening in the other browsers that I'm using.

    The log entries your mentioning are as expected:

    Code:
     May 24, 2011 12:17:31 AM org.icepush.servlet.EnvironmentAdaptingServlet <init>
     INFO: Adapting to Servlet 3.0 AsyncContext environment
     May 24, 2011 12:17:31 AM org.icepush.servlet.AsyncAdaptingServlet <init>
     INFO: Using Servlet 3.0 AsyncContext
     May 24, 2011 12:17:31 AM org.icepush.servlet.EnvironmentAdaptingServlet service
     INFO: Falling back to Thread Blocking environment
     

    And Server Push should work with these log entries.

    Can you post your ICEfaces Configuration? Which is a log entry as well similar to this:

    Code:
     May 24, 2011 12:15:56 AM org.icefaces.util.EnvConfig init
     INFO: ICEfaces Configuration: 
     org.icefaces.render.auto: true [default]
     org.icefaces.autoid: true [default]
     org.icefaces.aria.enabled: true [default]
     org.icefaces.blockUIOnSubmit: false [default]
     org.icefaces.compressDOM: false [default]
     org.icefaces.compressResources: true [default]
     org.icefaces.connectionLostRedirectURI: null [default]
     org.icefaces.deltaSubmit: false [default]
     org.icefaces.lazyPush: true [default]
     org.icefaces.sessionExpiredRedirectURI: null [default]
     org.icefaces.standardFormSerialization: false [default]
     org.icefaces.strictSessionTimeout: false [default]
     org.icefaces.windowScopeExpiration = 1000 [default]
     org.icefaces.mandatoryResourceConfiguration: null [default]
     org.icefaces.uniqueResourceURLs: true [default]
     org.icefaces.lazyWindowScope: true [default]
     org.icefaces.disableDefaultErrorPopups: false [default]
     

    Which ICEfaces libraries are included in the application's WEB-INF/lib/ directory?

    Regards,
     
    Profile for jack.van.ooststroom -> Messages posted by jack.van.ooststroom [223] Go to Page: 1, 2, 3  ...  13, 14, 15 Next 
    Go to:   
    Powered by JForum 2.1.7ice © JForum Team