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

[Dan Allen (JIRA)]

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

Dan Allen commented on JBIDE-3623:
----------------------------------

I haven't dove into the details, but some how Seam 2.1 is more aggressive in resolving the hot deploy path. My guess is that in Seam 2.0 it simply could not find it in the test execution environment and thus never used it. Clearly in Seam 2.1 it is being used.

So when the same class file is loaded but two different classloaders, how can you tell it came from the same file location? Given the abstract at which the Seam deployment scanner works, I'm not sure it is simple to figure this out. I still say that it is better if we just ensure that the two classloaders don't try to use the same location. But I'm speaking at a high level.

> 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: Dan Allen
>            Priority: Blocker
>             Fix For: 3.0.0.GA, 3.0.1.GA, 3.1.0
>
>
> 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