Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1146853 - Proxy naming conflict when using static nested classes with the same name and package
Proxy naming conflict when using static nested classes with the same name and...
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CDI/Weld (Show other bugs)
6.3.0
Unspecified Unspecified
unspecified Severity unspecified
: DR5
: EAP 6.4.0
Assigned To: Jozef Hartinger
Adela
:
Depends On: 1148811
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-26 04:50 EDT by Jozef Hartinger
Modified: 2018-03-06 15:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of EAP if two static nested classes with equal names enclosed by different classes were used as beans, Weld generated proxies with equal class names for both such beans and `ClassCastException` were thrown when such beans were used. This was fixed by amending the proxy class name generation procedure to include the name of the enclosing class. Two static nested classes can now have the same simple class name even when enclosed by two different classes in the same package.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WELD-1558 Major Resolved Proxy naming conflict when using static nested classes with the same name and package. 2015-07-30 08:41:19 EDT

  None (edit)
Description Jozef Hartinger 2014-09-26 04:50:53 EDT
See https://issues.jboss.org/browse/WELD-1558 for details
Comment 1 Kabir Khan 2014-10-08 08:11:12 EDT
Fixed by 1.1.26 upgrade 1148811
Comment 2 Ron Šmeral 2014-10-14 13:15:02 EDT
Verified in 6.4.0.DR5.

Note You need to log in before you can comment on or make changes to this bug.