Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: future release
    • Component/s: admin
    • Labels:
      None
    • Environment:

      Generic

      Description

      During upgrades and updates from prior releases it has been necessary
      for the server to (1) determine the version of GF the domain.xml file is
      supporting (e.g. v2.1, 3.0.1, etc) and (2) make adjustments to the contents
      of the file in preparation to support the current version of GF.

      We have employed various methods to determine the current version of
      the domain.xml file such as looking for the absence of certain
      required elements.

      By adding a new "version" element or attribute which represents the
      version of the file this could assist future versions of GF during
      update and upgrade procedures. It would provide a reliable way to detect
      the version of the file.

        Activity

        Chris Kasso created issue -
        Hide
        Tom Mueller added a comment -

        Note that the <domain> element in the domain.xml today has a "version" attribute. It is set to "10.0" in the domain.xml template, and any domains created with the asadmin create-domain command will have that value for the version.

        However, private and release engineering builds of the software insert different values, such as "re-continuous", into this attribute for the "domain1" that is created at build time. It is not clear what this version value is supposed to represent. It appears to be the version of the software that was initially there when the domain was created, since the value is never updated once it is written to the domain, even if the software is updated using the package system.

        A version identification for the purposes of upgrade will need to use a different version field.

        Show
        Tom Mueller added a comment - Note that the <domain> element in the domain.xml today has a "version" attribute. It is set to "10.0" in the domain.xml template, and any domains created with the asadmin create-domain command will have that value for the version. However, private and release engineering builds of the software insert different values, such as "re-continuous", into this attribute for the "domain1" that is created at build time. It is not clear what this version value is supposed to represent. It appears to be the version of the software that was initially there when the domain was created, since the value is never updated once it is written to the domain, even if the software is updated using the package system. A version identification for the purposes of upgrade will need to use a different version field.
        Tom Mueller made changes -
        Field Original Value New Value
        Fix Version/s 3.2 [ 10969 ]
        Tags 3_1-exclude
        Hide
        Tom Mueller added a comment -

        A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.

        Show
        Tom Mueller added a comment - A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.
        Tom Mueller made changes -
        Fix Version/s future release [ 11148 ]
        Fix Version/s 3.2 [ 10969 ]
        Tom Mueller made changes -
        Assignee Tom Mueller [ tmueller ] kumara [ kumara ]

          People

          • Assignee:
            kumara
            Reporter:
            Chris Kasso
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: