glassfish
  1. glassfish
  2. GLASSFISH-6062

params in a line in domains.xml not in the same order

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: V3
    • Fix Version/s: None
    • Component/s: admin
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      6,062
    • Status Whiteboard:
      Hide

      gfv3-prelude-included

      Show
      gfv3-prelude-included

      Description

      I open domains.xml from a fresh installation (any build ..they are the same).

      you will see this line

      <http-listener id="http-listener-1" address="0.0.0.0" port="8080"
      acceptor-threads="1" security-enabled="false" default-virtual-server="server"
      server-name="" xpowered-by="true" enabled="true" family="inet"
      blocking-enabled="false">

      if I start the server.. the config will be loaded and resave (maybe by the admin
      gui.. )

      and the line will become

      <http-listener id="http-listener-1" port="8080" xpowered-by="true"
      enabled="true" address="0.0.0.0" security-enabled="false" family="inet"
      default-virtual-server="server" server-name="" blocking-enabled="false"
      acceptor-threads="1">

      the order of the params should stay the same.

        Activity

        Hide
        kumara added a comment -

        v3 defect tracking

        Show
        kumara added a comment - v3 defect tracking
        Hide
        Tom Mueller added a comment -

        The GlassFish server doesn't make any claims about what order the elements in the domain.xml are written, as long as it is valid XML. The attributes are actually written in the order that they are declared within the config bean, but that is an implementation detail and not part of the interface to the product.

        Marking as "won't fix".

        Show
        Tom Mueller added a comment - The GlassFish server doesn't make any claims about what order the elements in the domain.xml are written, as long as it is valid XML. The attributes are actually written in the order that they are declared within the config bean, but that is an implementation detail and not part of the interface to the product. Marking as "won't fix".

          People

          • Assignee:
            Tom Mueller
            Reporter:
            survivant
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: