[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3996) Seam should ignore duplicate classes on classpath

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Mar 7 14:49:22 EST 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456042#action_12456042 ] 

Pete Muir commented on JBSEAM-3996:

No, thats wrong

"one component could override another with the same component name and class"

Same name yes, exactly the same class, no. A sub/superclass yes, or the same class defined in XML (but we are way before XML kicks in here). There is absolutely no way we want to be deploying the same class twice using annotations. This is not well defined in Seam, I know, but it is implied.

> Seam should ignore duplicate classes on classpath
> -------------------------------------------------
>                 Key: JBSEAM-3996
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3996
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0.SP1, 2.1.1.GA
>            Reporter: Max Rydahl Andersen
>            Assignee: Dan Allen
>             Fix For: 2.1.2.GA
> As discussed in JBIDE-3623 then Seam is reporting "Two components with the same name and precedence - component name: <name>, component classes: <classname>" when the class name is exactly the same. In that case it should only be the one that is first on the classpath that is used; that the class exist in other locations is irrelevant since you won't be able to load the class anyway since in java classloading first-found wins.

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 seam-issues mailing list