2 Replies Latest reply on Jan 20, 2012 3:58 AM by Lukáš Fryč

    Simplifying RichFaces Push configuration

    Lukáš Fryč Master

      From the responses on forums, it seems RichFaces Push is hard to start up with, despite it's quite simple concept to use.

       

      Following post covers whole situation and offers solution.

       

      Current sources for documentation are:

       

       

      From following forum posts, I got feeling it's really not enought:

       

      ==============================

       

      I have created issue for simplifying Push documentation ( https://issues.jboss.org/browse/RFPL-1980 ) already and I will brain-storm about the possible ways how to achieve that there.

       

      I have also created article how to start with various containers which is more accurate than current docs and information there could be used as basis for simplified documentation.

       

      ==============================

       

      Question is what we can do on configuration/impl side for making a start simpler:

       

      1. Push JMS integration should be made optional (turned off by default)
      2. Push topics initialization
        • initialization composed from two parts, which are currently handled programatically by user-defined TopicsInitializer
        • 1. Re: Simplifying RichFaces Push configuration
          Brian Leathem Master

          1. Given that push without JMS will work in all cases, it is indeed the sensible default.  Users can optionaly "upgrade" to using JMS. We'll just have to make sure we announce this backward incompatibility well with the release.

           

          2. Initialising the topics lazily seems like a good route, making it easy for developers to consume the feature.  However, alloing users to additionally configure topics via the web.xml may be useful as a performance optimisation.

          • 2. Re: Simplifying RichFaces Push configuration
            Lukáš Fryč Master

            +1

            Brian Leathem wrote:

             

            2. Initialising the topics lazily seems like a good route, making it easy for developers to consume the feature.  However, alloing users to additionally configure topics via the web.xml may be useful as a performance optimisation.

            Yes, user can still optimize that using TopicsInitializer.

             

            Lets open feature request once we will see the need for that.