You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2010/10/21 11:19:17 UTC

[jira] Created: (MYFACES-2952) Improve Atmosphere Meteor support of MyFaces

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.

[jira] Commented: (MYFACES-2952) Improve Atmosphere Meteor support of MyFaces

Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
    [ 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.

[jira] Resolved: (MYFACES-2952) Improve Atmosphere Meteor support of MyFaces

Posted by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/MYFACES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-2952.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-SNAPSHOT
         Assignee: Leonardo Uribe

Added org.apache.myfaces.INITIALIZE_ALWAYS param as suggested on the list.

> 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
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.3-SNAPSHOT
>
>
> 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.

[jira] Commented: (MYFACES-2952) Improve Atmosphere Meteor support of MyFaces

Posted by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/MYFACES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928316#action_12928316 ] 

Leonardo Uribe commented on MYFACES-2952:
-----------------------------------------

Just as a small comment and by historical purposes, the final name for this param is org.apache.myfaces.INITIALIZE_ALWAYS_STANDALONE, as corrected by Matthias

> 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
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.3-SNAPSHOT
>
>
> 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.