Project

General

Profile

Story #1403

case insensitive parameter support in MultipartRequestResolver

Added by Rob Nahf almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Rob Nahf
Category:
d1_common_java
Target version:
Sprint-2011.21-Block.3
Start date:
Due date:
% Done:

100%

Story Points:
Sprint:

Description

the architecture specifies that Rest parameters are case insensitive, so the map keys to the multipart parameters (and files) need to be case standardized as they are created (suggest lowercase) in order to be able to pull them out efficiently. Otherwise, clients would have to ask for 'PID', 'Pid', or 'pid' in order to make sure they are getting what they need.

Users of MultiPartRequestResolver will need to make code changes as well.

Subtasks

Task #1500: review arch docs to make sure parameters follow the same format (camelText)ClosedDave Vieglais

Task #1499: review metacat handlers to remove case-standardizing logic and ensure proper case-sensitive mappingClosedRob Nahf

History

#1 Updated by Rob Nahf almost 14 years ago

  • Category set to d1_common_java
  • Assignee set to Rob Nahf

#2 Updated by Dave Vieglais almost 14 years ago

  • Target version changed from Sprint-2011.10-Block.2 to Sprint-2011.11-Block.2
  • Position set to 4
  • Position deleted (32)

#3 Updated by Dave Vieglais almost 14 years ago

  • Position deleted (5)
  • Position set to 2
  • Target version changed from Sprint-2011.11-Block.2 to Sprint-2011.12-Block.2

#4 Updated by Dave Vieglais almost 14 years ago

  • Position set to 1
  • Position deleted (6)
  • Target version changed from Sprint-2011.12-Block.2 to Sprint-2011.13-Block.2

#5 Updated by Dave Vieglais almost 14 years ago

  • Target version changed from Sprint-2011.13-Block.2 to Sprint-2011.14-Block.2
  • Position set to 1
  • Position deleted (16)

#6 Updated by Dave Vieglais almost 14 years ago

There was some discussion on this some time in January or February and the general consensus was to make the parameter keys and values case sensitive, with preference for lower case keys.

In all cases, the description of the method signatures, type names, or properties as described in the types XML Schema should be considered first, followed by the API documentation. Where conflicts occur, the types XML Schema will predominate.

#7 Updated by Dave Vieglais almost 14 years ago

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

#8 Updated by Dave Vieglais almost 14 years ago

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

#9 Updated by Dave Vieglais over 13 years ago

  • Position set to 1
  • Position changed from 1 to 188
  • Position deleted (14)
  • Target version changed from Sprint-2011.17-Block.3 to Sprint-2011.18-Block.3

#10 Updated by Robert Waltz over 13 years ago

  • Target version changed from Sprint-2011.18-Block.3 to Sprint-2011.19-Block.3
  • Position set to 28
  • Position deleted (191)

#11 Updated by Dave Vieglais over 13 years ago

  • Target version changed from Sprint-2011.19-Block.3 to Sprint-2011.20-Block.3
  • Position deleted (28)
  • Position set to 3

#12 Updated by Dave Vieglais over 13 years ago

  • Target version changed from Sprint-2011.20-Block.3 to Sprint-2011.21-Block.3
  • Position set to 1
  • Position deleted (12)

#13 Updated by Dave Vieglais over 13 years ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)