ICEfaces
  1. ICEfaces
  2. ICE-2868

ICEfaces AHS: The JMS Topics should be configurable (follow up)

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.7
          • Fix Version/s: 1.8.2-EE-GA_P01, 1.8.3
          • Component/s: None
          • Labels:
            None
          • Environment:
            ICEfaces Asynchronous HTTP Server

            Description

            The JMS Topic names should be made configurable to be used by the developer.

            This is a follow up to ICE-2214.

              Issue Links

              blocks

              Improvement - An improvement or enhancement to an existing feature or task. IPCK-62 Stop using topic names explicitly and rely on the default topic used by the Message Service Client

              • Major - Major loss of function.
              • Closed
              depends on

              Improvement - An improvement or enhancement to an existing feature or task. ICE-2214 ICEfaces AHS: The JMS Topics should be configurable and have a default value that works across application servers

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Changed Fix Version(s) to 1.7.1

                Show
                Jack Van Ooststroom added a comment - Changed Fix Version(s) to 1.7.1
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Changed Assignee Priority to P3; this might be out-of-scope for this release

                Show
                Jack Van Ooststroom added a comment - Changed Assignee Priority to P3; this might be out-of-scope for this release
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Re-targeted for ICEfaces 2.0

                Show
                Jack Van Ooststroom added a comment - Re-targeted for ICEfaces 2.0
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Changed Fix Version(s) to 1.8.3 and 1.8.2-EE-GA_P01

                Show
                Jack Van Ooststroom added a comment - Changed Fix Version(s) to 1.8.3 and 1.8.2-EE-GA_P01
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                In the AHS days we initially had multiple different topics specific to ICEfaces that we used. The current MSC API still reflects that by having the requirement of specifying the topic name whenever a message needs to be published and such. Now the MSC uses a default topic name, namely "icefacesPush", which is configurable through an ICEfaces applications web.xml by setting the com.icesoft.net.messaging.defaultTopicName context parameter to the desired value. In order to use the default topic either the traditional API can be used passing the MessageServiceClient.getDefaultTopicName() as the topic name, or the new API which doesn't require the specification of a topic name and will use the default topic automatically. This preserves the flexibility of the API and introduces simplified overloaded methods. Marking this one as FIXED.

                Show
                Jack Van Ooststroom added a comment - In the AHS days we initially had multiple different topics specific to ICEfaces that we used. The current MSC API still reflects that by having the requirement of specifying the topic name whenever a message needs to be published and such. Now the MSC uses a default topic name, namely "icefacesPush", which is configurable through an ICEfaces applications web.xml by setting the com.icesoft.net.messaging.defaultTopicName context parameter to the desired value. In order to use the default topic either the traditional API can be used passing the MessageServiceClient.getDefaultTopicName() as the topic name, or the new API which doesn't require the specification of a topic name and will use the default topic automatically. This preserves the flexibility of the API and introduces simplified overloaded methods. Marking this one as FIXED.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Jack Van Ooststroom
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: