[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3623) TestNG for Seam 2.1.0 SP1 war project.

Steve Lee (JIRA) jira-events at lists.jboss.org
Tue Feb 3 03:15:44 EST 2009


    [ https://jira.jboss.org/jira/browse/JBIDE-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450767#action_12450767 ] 

Steve Lee commented on JBIDE-3623:
----------------------------------

I have reproduced the issue under the following environment:

Windows Vista SP1
Eclipse 3.4
Seam 2.1.1GA
JbossTool Clipse Plugin 3.0.0CR2
Java 1.5.0_16

Can someone provide a workaround?  Everybody will encounter this scenario just in the very first day of trying Seam. 

What I did was this:
Create a Seam Project under Eclipse
Seam generated the entity from existing DB
Added a Seam Action by using Eclipse JbossTool
Run TestNG on ActionLocalTest.xml generated by Seam Action code.

The error log is as follows:

[Parser] Running:
  C:\Users\ian\workspace34mian\firstSeam-test\test-src\org\domain\firstseam\test\ActionLocalTest.xml

FAILED CONFIGURATION: @BeforeSuite startSeam
java.lang.IllegalStateException: Two components with the same name and precedence - component name: groupUsersHome, component classes: org.domain.firstseam.session.GroupUsersHome, org.domain.firstseam.session.GroupUsersHome
	at org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:596)
	at org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:949)
	at org.jboss.seam.init.Initialization.installHotDeployableComponents(Initialization.java:847)
	at org.jboss.seam.init.Initialization.init(Initialization.java:725)
	at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:919)
	at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
... Removed 15 stack frames
SKIPPED CONFIGURATION: @BeforeClass setupClass
SKIPPED CONFIGURATION: @BeforeMethod begin
SKIPPED CONFIGURATION: @AfterMethod end
SKIPPED CONFIGURATION: @AfterClass cleanupClass
SKIPPED: test_actionMethod


> TestNG for Seam 2.1.0 SP1 war project.
> --------------------------------------
>
>                 Key: JBIDE-3623
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3623
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.0.0.CR2
>         Environment: WindowsXP SP2
> JBoss Developer Studio
> Version: 2.0.0.CR2
> Build id: jbdevstudio-eap-win32-2.0.0.CR2-N200901221952
> JRE 1.5_08
>            Reporter: Aliaksey Nis
>            Assignee: Pete Muir
>             Fix For: 3.0.0.GA
>
>
> EXECUTE: Create Seam 2.1.0 SP1 war project.
> EXECUTE: Create action for this project.
> EXECUTE: Run test NG for this action.
> FAILURE: Tests failed. Exception appears in console view .
> AILED CONFIGURATION: @BeforeSuite startSeam
> java.lang.IllegalStateException: Two components with the same name and precedence - component name: authenticator, component classes: org.domain.seam21war.session.Authenticator, org.domain.seam21war.session.Authenticator
> 	at org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:586)
> 	at org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:927)
> 	at org.jboss.seam.init.Initialization.installHotDeployableComponents(Initialization.java:797)
> 	at org.jboss.seam.init.Initialization.init(Initialization.java:716)
> 	at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:920)
> 	at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
> ... Removed 15 stack frames
> SKIPPED CONFIGURATION: @BeforeClass setupClass
> SKIPPED CONFIGURATION: @BeforeMethod begin
> SKIPPED CONFIGURATION: @AfterMethod end
> SKIPPED CONFIGURATION: @AfterClass cleanupClass
> SKIPPED: test_action1

-- 
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