Project

General

Profile

Bug #7383

CN.registerNode() fails when nodeReplicationPolicy is partially present

Added by Ben Leinfelder over 8 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
d1_cn_noderegistry
Target version:
-
Start date:
2015-09-23
Due date:
% Done:

0%

Story Points:
Sprint:

Description

Andrei submitted a Node document to cn-dev-2 for registration, but it was rejected because the registration code only checked if NodeReplicationPolicy was null before trying to access other properties of the policy (that were absent).
His Node xml simply had:

The schema does not require any child elements:
http://jenkins-1.dataone.org/jenkins/job/API%20Documentation%20-%20trunk/ws/api-documentation/build/html/apis/Types.html#Types.NodeReplicationPolicy

We should ensure that schema-valid Node documents are accepted, even if they do not necessarily make sense. In this case, there was no information provided. The schema probably should require at least one child element otherwise what is the point of including it? But I'm afraid we can't change the schema at this point.


Related issues

Duplicates Infrastructure - Bug #7379: GMN could not save Node document with null NodeReplicationPolicy.max size property Closed 2015-09-23

History

#1 Updated by Ben Leinfelder over 8 years ago

  • Status changed from New to Rejected

duplicate of 7379

#2 Updated by Ben Leinfelder over 8 years ago

  • Duplicates Bug #7379: GMN could not save Node document with null NodeReplicationPolicy.max size property added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)