[RANGER-346] Service-def files update to use map for *Options fields, instead of a string with custom format

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Component/s: admin
• Assignee: Madhan Neethiraj
• Reporter: Madhan Neethiraj
• Created: 28/Mar/15 00:18
• Updated: 28/Mar/15 02:14
• Resolved: 28/Mar/15 02:14

Description

Currently the embedded service-def JSON files use string field, with a custom format, to specify name-value pairs in the following fields:

• matcherOptions
• evaluatorOptions
• enricherOptions

To be consistent with JSON, these fields need to be updated to use Map.

In addition:

• the resource-levels are specified as "1", "2", "3". To enable easier addition of resources, it will be better to use values "10", "20", 30"
• fix misspelled option 'pathSeperatorChar' to 'pathSeparatorChar'