#274 closed defect (released)
crash when missing unitMember id
Reported by: | Henri | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | WarFoundry 0.1 |
Component: | WarFoundry-API | Version: | Trunk |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #290 |
Description
If the datafile refers to an unitMemebr id that does not exist, e.g. due to a typo then the program crashes.
It states something like a "null pointer error" or whatever.
Change History (14)
comment:1 Changed 10 years ago by
Status: | new → confirmed |
---|
comment:2 Changed 10 years ago by
comment:3 Changed 10 years ago by
comment:4 Changed 10 years ago by
Validation isn't working for some reason. key/keyref pair should enforce correct referencing, where as ID and IDREF as type just requires reference to any ID anywhere in the document. Still investigating.
comment:5 Changed 10 years ago by
comment:6 Changed 10 years ago by
comment:7 Changed 10 years ago by
Problem all seems to be down to the fact that the schema validation will happily reject invalid files based on unexpected tags, but document.SchemaInfo.Validity is NotKnown.
comment:8 Changed 10 years ago by
Not useful - the MSDN example reports Valid on Windows and NotKnown on Mono. More investigation is required.
comment:9 Changed 10 years ago by
comment:10 Changed 10 years ago by
Blocking: | 290 added |
---|
comment:11 Changed 10 years ago by
(In r590) Re #274: Crash when missing unit member ID
- Add key and keyref for member type
Re #290: Migrate to using key/keyref definitions instead of ID/IDREF type
- Move keyref and key for equipment slot to correct place to be valid
- Add aliased xmlns for schema to allow for use in XPath, which doesn't use default namespace
- Disable warning reporting until Mono Bug 613684 is fixed (https://bugzilla.novell.com/show_bug.cgi?id=613684)
comment:12 Changed 10 years ago by
comment:14 Changed 9 years ago by
Resolution: | fixed → released |
---|
Retro-actively tag RC1 releases as released
Looks like we need better validation, as it should already pull it in as an ID reference. Probably occurs because the typo was a different ID elsewhere in the file.