Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8159

precedence doesn't work for the component properties specified in components.xml

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.2.0
    • Component/s: Seam2
    • Labels:
      None
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      Seam component precedence defined in the <filename>components.xml</filename> file was not taken into account when initializing component properties. If a property of the same component was defined more than once in the file, the last occurrence in the file was used, not the one defined in the <systemitem>&lt;component&gt;</systemitem> element with the highest value of the <systemitem>precedence</systemitem> attribute. This behaviour is now fixed and the property value defined in the <systemitem>&lt;component&gt;</systemitem> element with the highest precedence is used during component initialization.
      Show
      Seam component precedence defined in the <filename>components.xml</filename> file was not taken into account when initializing component properties. If a property of the same component was defined more than once in the file, the last occurrence in the file was used, not the one defined in the <systemitem>&lt;component&gt;</systemitem> element with the highest value of the <systemitem>precedence</systemitem> attribute. This behaviour is now fixed and the property value defined in the <systemitem>&lt;component&gt;</systemitem> element with the highest precedence is used during component initialization.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      Precedence doesn't work for the component's properties specified in components.xml. Component's attributes like class for example are taken according precedence but properties are taken from last loaded components.xml.

      ex)
      I put 2 component tag in components.xml. Despite value of precedence, name property was always set to last value (Component1Low).
      (The class of component1 followed the precedence (sample.Component2).)

      <component name="component1"
      class="sample.Component2"
      precedence="30">
      <property name="name">Component1High</property>
      </component>
      <component name="component1"
      class="sample.Component1"
      precedence="10">
      <property name="name">Component1Low</property>
      </component>

        Gliffy Diagrams

          Attachments

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. JBSEAM-3138 precedence doesn't work for the component properties specified in components.xml

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  tkonishi Takayuki Konishi
                  Writer:
                  Petr Penicka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: