Allow no rest mappings to be supplied

[bdw429s]

I've had a hacky workaround in place ever since the --servlet-rest-mappings arg was added in:

// Runwar will blow up if there isn't a parameter supplied, so I can't pass an empty string.
if( len( serverInfo.restMappings ) ) {
	args.append( '--servlet-rest-mappings' ).append( serverInfo.restMappings );
} else {
	// This effectively disables it (assuming there's not a real directory or route called "___disabled___") but it's janky
	args.append( '--servlet-rest-mappings' ).append( '___DISABLED___' );
}

I don't recall the error right off, but I'd like to be able to just omit the --servlet-rest-mappings when none are specified (which is the default in CommandBox)

[denuno]

Looks like I added a value check for that a while back, you can pass it an empty string now I believe.

[bdw429s]

@denuno Nope. I just tried it and if I provide an empty string for the rest mapping, then the default rest mappings kick in. I don't want there to be any rest mapping by default unless the user explicitly configures them.

 --servlet-rest-mappings ""

[INFO ] runwar.server: Overriding web.xml rest mappings with [/rest]
[INFO ] runwar.server: Added rest mapping: /rest to CFRestServlet

[denuno]

Does --servlet-rest-enable not work?

[bdw429s]

Nope, that doesn't seem to do it. With this JVM arg in place:

 --servlet-rest-enable false

I see this in the console logs:

[INFO ] runwar.server: Overriding web.xml rest mappings with [/rest]
[INFO ] runwar.server: Added rest mapping: /rest to CFRestServlet