Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-5685

Invalid Duplicate component name validation error

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.1.0.CR1
    • Fix Version/s: 3.1.0.CR2
    • Component/s: seam2
    • Labels:
      None

      Description

      Working from Seam In Action examples, but now with SEAM 2.2 and tools 3.1 CR1.

      RegisterAction uses some additional configuration from components.xml, defined by a component element without a class specified;

      <component name="registerAction">
      <property name="pro-status-types">amateur pro semi-pro</property>
      <property name="specialtyTypes">
      <value>#

      {messages['specialty.drive']}

      </value>
      <value>#

      {messages['specialty.chip']}

      </value>
      <value>#

      {messages['specialty.putt']}

      </value>
      <value>#

      {messages['specialty.iron']}

      </value>
      <value>#

      {messages['specialty.looks']}

      </value>
      </property>
      </component>

      The RegisterAction java source is annotated with an @Name header:

      package org.open18.action;

      ...

      @Name("registerAction")
      public class RegisterAction {

      Validation flags this as "Duplicate component name: "registerAction".

      This does not prevent the project from building or deploying to JBoss AS 5.1, which in fact operates correctly. The validation simply flags it as an error.
      This same validation works properly in Seam 2.1 and tools 3.0.1.GA-R2.

      Updated to the latest nightly build (JBossTools-Update-3.1.0.v201001140301N-H131-CR2.zip) and the problem still exists.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                akazakov Alexey Kazakov
                Reporter:
                sage.sam David Hibbs
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: