Story #7422
Invalid system metadata with some CN system metadata entries
Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_cn_common
Target version:
Start date:
2015-10-12
Due date:
% Done:
100%
Story Points:
Sprint:
Description
It appears that Jibx serializer generates invalid XML for some system metadata entries. There are two (common) cases that are problematic:
- Null elements are actually serialized as elements with zero length string.
Example: peggym.38.1
urn:node:KNB
is invalid because blockedMemberNode is of type d1:NonEmptyString. The blockedMemberNode entry should not be present if empty.
- Container elements with no entries are serialized as an empty element instead of null.
Example: ajpelu.4.1
is invalid because accessPolicy should container 1 or more AccessRule entries
Subtasks
History
#1 Updated by Dave Vieglais about 9 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
#2 Updated by Robert Waltz over 8 years ago
- Assignee changed from Dave Vieglais to Robert Waltz
#3 Updated by Robert Waltz over 8 years ago
- Target version set to CCI-2.2.0
#4 Updated by Robert Waltz over 8 years ago
- Project changed from Infrastructure to CN REST
- Category deleted (
d1_schemas)
#5 Updated by Robert Waltz over 8 years ago
- Category set to d1_cn_common
#6 Updated by Robert Waltz over 8 years ago
- % Done changed from 30 to 50
- Status changed from In Progress to Testing
#7 Updated by Robert Waltz over 8 years ago
- % Done changed from 50 to 100
- Status changed from Testing to Closed
