[richfaces-planning-issues] [JBoss JIRA] (RFPL-2078) Component reference - a4j:push - small typos

[Juraj Huska (JIRA)]

     [ https://issues.jboss.org/browse/RFPL-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj Huska moved RF-11998 to RFPL-2078:
----------------------------------------

              Project: RichFaces Planning  (was: RichFaces)
                  Key: RFPL-2078  (was: RF-11998)
             Workflow: jira  (was: GIT Pull Request workflow )
    Affects Version/s: 4.2.0.Final
                           (was: 4.2.0.Final)
          Component/s: doc
                           (was: doc)
                           (was: component-push/poll)

    
> Component reference - a4j:push - small typos
> --------------------------------------------
>
>                 Key: RFPL-2078
>                 URL: https://issues.jboss.org/browse/RFPL-2078
>             Project: RichFaces Planning
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: doc
>    Affects Versions: 4.2.0.Final
>         Environment: Component reference
>            Reporter: Juraj Huska
>            Priority: Trivial
>
> I have found these typos and other things which should be IMHO corrected for the _a4j:push_ in _Component Reference_.
> CURRENT: When you are registering Push servlet in the Servlets 3.0 environments manually, the RichFaces will detect that servlet for Push is already registered and it avoids to initialize it again.
> However be sure to setup the Push servlet to support asynchronous requests - modify the servlet registration in the previous web.xml snippet as follows:
> MAYBE: When you *attempt to register* Push servlet *manually* in the Servlets 3.0 environments, the RichFaces will detect that servlet for Push is already registered*, and* it *avoids initializing* it again.
> *However, be sure* to setup the Push servlet to support asynchronous requests - modify the servlet registration *from* the previous web.xml snippet as follows:
> CURRENT: Sending a message using the TopicsContext involves creating a TopicKey instance (denominator of given message topic) and looking up the TopicsContext used for topic registration and message publishing.
> MAYBE: Sending a message using the TopicsContext*, which was used for registration of topic and message publishing,* involves creating a TopicKey instance (denominator of given message topic) and *look the TopicContext up*.
> CURRENT: Ensure the Create durable subscriber and Delete durable subscriber options are set to true for push functionality.
> MAYBE: Ensure the Create durable subscriber and *the* Delete durable subscriber options are set to true for *proper* push functionality.
> CURRENT: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by default
> MAYBE: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by *default.*
> CURRENT: The JMS message which should be propagated to Push needs to be created with method session.createObjectMessage(message);.
> MAYBE: The JMS message which should be propagated to Push needs to be created with *the* method session.createObjectMessage(message);.
> CURRENT: Receiving messages from JMS doesn't differ from receiving messages sent by the TopicsContext or using CDI events.
> MAYBE: Receiving messages from *a JMS queues* doesn't differ from *the* receiving messages sent by the TopicsContext or using a CDI events.
> CURRENT: This example demonstrates a simple use of the <a4j:push> causing an immediate update of page content.
> MAYBE: *The example above* demonstrates a simple use of the <a4j:push> causing an immediate update of *the* page content.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira