It is possible to implement Grizzly integration without any configuration of the web application (because APIs can be used directly) however, the initial version of this integration will still use a manually configured servlet to reduce the risk of interaction with the prototype code.

The initial checkin requires configuration in web.xml as follows:

<servlet>
<servlet-name>Grizzly Push Servlet</servlet-name>
<servlet-class>com.icesoft.faces.webapp.http.servlet.GrizzlyPushServlet</servlet-class>
<load-on-startup> 1 </load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>Grizzly Push Servlet</servlet-name>
<url-pattern>/block/receive-updated-views/*</url-pattern>
</servlet-mapping>

There appear to be some significant timing-related problems with this initial version. Browser interaction is occasionally lost and push messages are sometimes lost.

GlassFish/Grizzly integration is now working well with auctionMonitor demo.