Project

General

Profile

Bug #1308

CRUD service interfaces do not allow InvalidRequest for create or update

Added by Rob Nahf almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
d1_common_java
Target version:
Start date:
Due date:
% Done:

100%

Milestone:
Product Version:
*
Story Points:
Sprint:

Description

This is a mistake, because it is very possible for the MMP to be malformed by the client. For a relevant example, recall the sysmeta vs. systemmetadata confusion for the name of the part containing the systemMetadata.

Currently GMN does throw an informative InvalidRequest exception, which was quite helpful for debugging the client code quickly.
Metacat follows the spec and throws a 500 error (ServiceFailure), but that masks the problem. (It's error description is "Error handling MMP upload: null", a bit less informative)

Recommend adding the InvalidRequest to the throws clause for:
1. CoordinatingNodeCrud.create
2. MemberNodeCrud.create
3. MemberNodeCrud.update


Subtasks

Task #1512: update the d1_common_java interfacesClosedRob Nahf

Task #1513: refactor d1_libclient_java to accomodate the new exceptionClosedRob Nahf

History

#1 Updated by Matthew Jones almost 11 years ago

  • Target version set to Sprint-2011.14-Block.2
  • Position set to 33

#2 Updated by Dave Vieglais almost 11 years ago

  • Position set to 2
  • Target version changed from Sprint-2011.14-Block.2 to Sprint-2011.15-Block.2
  • Position deleted (36)

#3 Updated by Dave Vieglais almost 11 years ago

  • Position deleted (2)
  • Position set to 4

#4 Updated by Dave Vieglais over 10 years ago

  • Position set to 1
  • Target version changed from Sprint-2011.15-Block.2 to Sprint-2011.17-Block.3
  • Position deleted (16)

#5 Updated by Rob Nahf over 10 years ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)