Bug #10148
ENUM class GETENUM NullPointerException when using poly types
Start date:
Due date:
% Done:
100%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Teodor Gorghe about 1 year ago
- % Done changed from 0 to 30
After revision 1770 on testcases, there is a test, tests.oo.basic.CustTypeEnum.
With the latest trunk build, the results in FWD are following:
Test results
The cause of this problem is
ObjectOps.getStaticInstance(Class), which makes the instance null.#3 Updated by Teodor Gorghe about 1 year ago
- Assignee set to Teodor Gorghe
Created task branch 10148a.
Committed revision 15982 on task branch 10148a:
- Fixed ObjectOps.invokePoly when using ENUM type.
#4 Updated by Teodor Gorghe about 1 year ago
- Status changed from New to WIP
#5 Updated by Teodor Gorghe about 1 year ago
- Status changed from WIP to Review
#6 Updated by Constantin Asofiei about 1 year ago
Where you do wa.staticReferents.put(cls, cls);, do also wa.referents2static.put(cls, cls); . This is missing now.
#7 Updated by Teodor Gorghe about 1 year ago
Committed revision 15983 on task branch 10148a:
- Addressed code review #10148-6
#8 Updated by Constantin Asofiei about 1 year ago
- Status changed from Review to Merge Pending
Please merge 10148a now.
#9 Updated by Teodor Gorghe about 1 year ago
- Status changed from Merge Pending to Test
Branch 10148a was merged to trunk rev 15985 and archived.
#10 Updated by Teodor Gorghe about 1 year ago
- % Done changed from 30 to 100