[
https://issues.apache.org/jira/browse/MYFACES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923381#action_12923381
]
Matthias Weßendorf commented on MYFACES-2952:
---------------------------------------------
A typical Meteor configuration would look like:
<servlet>
<description>MeteorServlet</description>
<servlet-name>MeteorServlet</servlet-name>
<servlet-class>org.atmosphere.cpr.MeteorServlet</servlet-class>
<init-param>
<param-name>org.atmosphere.servlet</param-name>
<param-value>javax.faces.webapp.FacesServlet</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useWebSocket</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useNative</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
Inside the "initFaces()" method of the AbstractFacesInitializer we could stop
aborting if the "org.atmosphere.servlet" of the
org.atmosphere.cpr.MeteorServlet does point to the (My)FacesServlet(s).
> Improve Atmosphere Meteor support of MyFaces
> --------------------------------------------
>
> Key: MYFACES-2952
> URL: https://issues.apache.org/jira/browse/MYFACES-2952
> Project: MyFaces Core
> Issue Type: Improvement
> Affects Versions: 2.0.3-SNAPSHOT
> Reporter: Matthias Weßendorf
>
> Currently MyFaces aborts the initialization when there is no configured
> "FacesServlet". While this does make sense in almost all cases, there are
> options when we do want the framework to initialize in a proper way:
> Atmoshpere's Meteor "framework" to support comet/websocket
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
