[
https://jira.jboss.org/jira/browse/JBSEAM-3996?page=com.atlassian.jira.pl...
]
Max Rydahl Andersen commented on JBSEAM-3996:
---------------------------------------------
What Pete Said :)
The "duplicate class" part is key, it is not a duplicate component.
I'm quite sure it was never intended for Seam to break normal classloading semantics.
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