[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4392) TestNG failed for Seam Action with exception: java.lang.IllegalStateException: Two components with the same name and precedence - component name: action1, component classes: org.domain.seamear2.session.Action1Bean, org.domain.seamear2.session.Action1Bean

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Fri May 29 11:33:56 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov resolved JBIDE-4392.
-----------------------------------

    Resolution: Rejected


It's not a bug. The code is not correct. You can't have two components with the same name.

> TestNG failed  for Seam Action with exception: java.lang.IllegalStateException: Two components with the same name and precedence - component name: action1, component classes: org.domain.seamear2.session.Action1Bean, org.domain.seamear2.session.Action1Bean
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4392
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4392
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.1.0.M1
>            Reporter: Anton Klimkovich
>
> EXECUTE: Create Seam Ear project
> EXECUTE: Create new Seam Action with nam action1 for example
> EXECUTE: Add string <component class="org.domain.seamear2.session.Action1Bean" name="action1"/> into components.xml
> EXECUTE: Run testNG for Action1Test.xml
> FAILURE:   TestNG failed  for Seam Action with exception: 
> java.lang.IllegalStateException: Two components with the same name and precedence - component name: action1, component classes: org.domain.seamear2.session.Action1Bean, org.domain.seamear2.session.Action1Bean
> 	at org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:543)
> 	at org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:809)
> 	at org.jboss.seam.init.Initialization.scanForComponents(Initialization.java:756)
> 	at org.jboss.seam.init.Initialization.init(Initialization.java:629)
> 	at org.jboss.seam.mock.BaseSeamTest.startSeam(BaseSeamTest.java:939)
> 	at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:923)
> 	at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82)
> 	at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:167)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:104)
> 	at org.testng.TestRunner.runWorkers(TestRunner.java:712)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:582)
> 	at org.testng.TestRunner.run(TestRunner.java:477)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:324)
> 	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:319)
> 	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292)
> 	at org.testng.SuiteRunner.run(SuiteRunner.java:198)
> 	at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823)
> 	at org.testng.TestNG.runSuitesLocally(TestNG.java:790)
> 	at org.testng.TestNG.run(TestNG.java:708)
> 	at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
> 	at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbosstools-issues mailing list