ICEfaces
  1. ICEfaces
  2. ICE-3045

ICEfaces AHS: Autodetect if AHS-related configurations are not set in the ICEfaces application's web.xml

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.7
          • Fix Version/s: 1.7.1
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces, ICEfaces-AHS

            Description

            If the icefaces-ahs.jar is present in an ICEfaces application's .war-file, it should try to use its functionality even if the ICEfaces application's web.xml does not contain the required AHS-related configurations.

              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 -

              Most of the work is done and checked in. However, detecting the right JMS properties file is only implemented for GlassFish at the moment. I still have to do this for our other support J2EE application servers.

              Show
              Jack Van Ooststroom added a comment - Most of the work is done and checked in. However, detecting the right JMS properties file is only implemented for GlassFish at the moment. I still have to do this for our other support J2EE application servers.
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              Detecting the right JMS properties file is now implemented for JBoss and clustered JBoss as well.

              To explain the detecting part of the right JMS properties a bit more in detail, the framework does the following at the moment:

              • If the com.icesoft.net.messaging.properties is not defined in the web.xml the framework examines the Server Info string to see which application server is used
              • If GlassFish is detected the default glassfish.properties is used; if this fails the framework cannot use the JMS functionalities automatically.
              • If JBoss is detected the default jboss_ha.properties is used first; if this fails because a clustered environment is not used the default jboss.properties is used instead; if this fails as well the framework cannot use the JMS functionalities automatically.

              I still have to add support for our other supported application servers, but this will be targeted for 1.7.2

              Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - Detecting the right JMS properties file is now implemented for JBoss and clustered JBoss as well. To explain the detecting part of the right JMS properties a bit more in detail, the framework does the following at the moment: If the com.icesoft.net.messaging.properties is not defined in the web.xml the framework examines the Server Info string to see which application server is used If GlassFish is detected the default glassfish.properties is used; if this fails the framework cannot use the JMS functionalities automatically. If JBoss is detected the default jboss_ha.properties is used first; if this fails because a clustered environment is not used the default jboss.properties is used instead; if this fails as well the framework cannot use the JMS functionalities automatically. I still have to add support for our other supported application servers, but this will be targeted for 1.7.2 Marking this one as FIXED.
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              JBoss auto-detection for the JMS properties fails on JBoss 4.0.x. Reopening this one.

              Show
              Jack Van Ooststroom added a comment - JBoss auto-detection for the JMS properties fails on JBoss 4.0.x. Reopening this one.
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              The Server Info string on JBoss 4.0.x starts with "Apache Tomcat". Auto-detection for JBoss 4.0.x is now updated. Marking this one as FIXED again.

              Show
              Jack Van Ooststroom added a comment - The Server Info string on JBoss 4.0.x starts with "Apache Tomcat". Auto-detection for JBoss 4.0.x is now updated. Marking this one as FIXED again.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: