Bug 696664
Summary: | Error when scheduling an operation when built with IntelliJ | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Heiko W. Rupp <hrupp> |
Component: | Core UI | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.0.0.Beta2 | CC: | ccrouch, hrupp, mazz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-03 16:55:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 730796 |
Description
Heiko W. Rupp
2011-04-14 14:59:38 UTC
java.lang.IllegalArgumentException: Argument 0 for @NotNull parameter of org/rhq/core/domain/resource/Resource.setName must not be null This looks like one of those "IntelliJ mucked with your bytecode" problems. Did you try again without IntelliJ modifying your .class bytecode? Yes this was one of those IJ thingies. Having said that: we must not keep things as is. Having a parameter marked somehow (does not matter if via annotation or comment) as "must not be null" and then passing null is just plain wrong. Either we remove the annotation from the code and are able to handle null. Or fix all the calls to that method to never pass null. (In reply to comment #2) > Yes this was one of those IJ thingies. > > Having said that: we must not keep things as is. Having a parameter marked > somehow (does not matter if via annotation or comment) as "must not be null" > and then passing null is just plain wrong. > Either we remove the annotation from the code and are able to handle null. Or > fix all the calls to that method to never pass null. I'm all for completely ripping out all IntelliJ-specific annotations. I never use them (in fact, no one using Eclipse can use them). To me, they add noise. In this particular case, it was null not because of anything we did. Looking at the stack, it looks to be nothing more than GWT attempting to serialize the object and it called setName with null. Not sure why, but it was GWT's serialization doing this, not us. [master a3f42a3] - remove NotNull annotations for the 'name' field, since it is not a required field according the DB schema for RHQ_RESOURCE. QE, this is a code change and does not need to be QA'ed. Bulk closing of old issues that are in VERIFIED state. |