I don't have Primefaces Push in production yet but we are planning to
migrate to it from DWR. We have tested it and it seems to work really well.
This is the configuration we have:
<servlet-name>Push Servlet</servlet-name>
<servlet-class>org.primefaces.push.PushServlet</servlet-class>
<async-supported>true</async-supported>
<init-param>
<param-name>org.atmosphere.cpr.broadcasterCacheClass</param-name>
<param-value>org.atmosphere.cache.UUIDBroadcasterCache</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.cpr.sessionSupport</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Push Servlet</servlet-name>
<url-pattern>/primepush/*</url-pattern>
</servlet-mapping>
On 9 January 2014 22:58, Howard W. Smith, Jr. <[email protected]>wrote:
> On Thu, Jan 9, 2014 at 1:52 PM, Romain Manni-Bucau <[email protected]
> >wrote:
>
> > Atmo works fine with last release
> >
>
> +1 the 2 reasons why I migrated from glassfish to tomee was
>
> 1. PrimeFaces Push (atmosphere) easily/definitely works with tomcat/tomee
>
> 2. migrate from JSF managed beans to CDI managed beans (via OpenWebBeans)
>
> and as said before tomee already uses tomcat websocket impl for websocket
> > spec
> >
>
> correct. see tomcat 7.0.37+ change logs and/or documentation
>
