Bugzilla – Full Text Bug Listing
| Summary: | NPE in XmlElementDefinitionByReference | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Greg Amerson <gregory.amerson> |
| Component: | Sapphire | Assignee: | Ling Hao <ling.hao> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | konstantin, ling.hao |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Fix checked in. Greg, I would appreciate it if you can verify my fix. Thanks! Verified NPE is fixed with build#336 Closing. Thanks for the problem report and verification. |
With my sapphire model that I've been using for several weeks all of a sudden (with latest updates) stopped working when trying to add a particular child element. Not every child element fails to be able to be inserted but sometimes I get a NPE down in XmlElementDefinitionByReference. here is where I'm seeing it: line 92 final XmlElementDefinition definition = getSchema().getElement(getName().getLocalPart()); This is sometimes returning a null value and the very next line will throw the NPE and this prevents the new child node from being added in the masterDetail page: if (definition.isAbstract()) { When I change this to add a null check everything seems to work ok. Sapphire is able to insert the new child element in the UI and in the source. if (definition != null && definition.isAbstract()) {