Weld
  1. Weld
  2. WELD-1065

Ambiguous name validation should not cross visibility boundaries

    Details

    • Affects:
      Release Notes
    • Similar Issues:
      Show 10 results 

      Description

      Caused by "additionalBeanDeploymentArchive" in the AS7 integration code that makes every two deployed beans transitively visible.

        Issue Links

          Activity

          Hide
          Frank Cornelis
          added a comment -

          Simple Arquillian based integration test that demonstrates the issue.

          Show
          Frank Cornelis
          added a comment - Simple Arquillian based integration test that demonstrates the issue.
          Hide
          Frank Cornelis
          added a comment -

          Did some additional tests. It's not only the @Named that gives ambiguous errors, but also simple @Produces methods that produce objects of the same type.

          Show
          Frank Cornelis
          added a comment - Did some additional tests. It's not only the @Named that gives ambiguous errors, but also simple @Produces methods that produce objects of the same type.
          Hide
          Luca Cavagnoli
          added a comment -

          How come this issue is marked as fixed in version 2.0.0.Alpha3? I've just tried the attached test case on jboss-as-7.1.1.Final-weld-2.0.0.Alpha3, and deployment still fails with the message:

          WELD-001414 Bean name is ambiguous. Name myBean resolves to beans [Managed Bean [class org.jboss.tools.examples.test.MyBean] with qualifiers [@Default @Any @Named], Managed Bean [class org.jboss.tools.examples.test.MyBean] with qualifiers [@Default @Any @Named]]

          Show
          Luca Cavagnoli
          added a comment - How come this issue is marked as fixed in version 2.0.0.Alpha3? I've just tried the attached test case on jboss-as-7.1.1.Final-weld-2.0.0.Alpha3, and deployment still fails with the message: WELD-001414 Bean name is ambiguous. Name myBean resolves to beans [Managed Bean [class org.jboss.tools.examples.test.MyBean] with qualifiers [@Default @Any @Named] , Managed Bean [class org.jboss.tools.examples.test.MyBean] with qualifiers [@Default @Any @Named] ]
          Hide
          Jozef Hartinger
          added a comment -

          The testcase is not valid. It is not portable to have multiple classes of the same name within the deployment. Weld currently does not support this but it's being done as part of WELD-1259. The valid testcase is at https://github.com/weld/core/blob/2.0/tests-arquillian/src/test/java/org/jboss/weld/tests/enterprise/validation/MultiwarProjectNameValidationTest.java

          Show
          Jozef Hartinger
          added a comment - The testcase is not valid. It is not portable to have multiple classes of the same name within the deployment. Weld currently does not support this but it's being done as part of WELD-1259 . The valid testcase is at https://github.com/weld/core/blob/2.0/tests-arquillian/src/test/java/org/jboss/weld/tests/enterprise/validation/MultiwarProjectNameValidationTest.java

            People

            • Assignee:
              Jozef Hartinger
              Reporter:
              Jozef Hartinger
            • Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: