[
https://jira.jboss.org/jira/browse/JBSEAM-3996?page=com.atlassian.jira.pl...
]
Max Rydahl Andersen reopened JBSEAM-3996:
-----------------------------------------
Looking at the patch I do not believe this will solve it.
The comparison should be based on the classname to avoid any problems with classpath order
and different classloaders.
Since Seam should only have access to *one* class within one classloader it should be
enough to compare the class name.
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: Marek Novotny
Priority: Critical
Fix For: 2.2.1.CR1
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