corrected the behaviour:
+ laboratorySearch and supportSearch, when 'sent' to the server, produce a request of the following form:
{
"search": {...}
}
instead of using their resource type ( i.e. { "laboratorySearch":{...}} )

+ The resourceType of the resource looked for is injected in the resource processor of the Root. This allows the 'search' resources to be properly processed on the way back
Deal with resource classes that register themselves N times

BaseResource.extendAs uses first element of array as resourceType
BaseResource.extendAs uses rest of array as registration names
BaseResource action handler defines resourceProcessor if unset
Use the class of resource for resourceProcessor
Or fallback to the resourceType if it can't be identified
Merge pull request #96 from mattdenner/correct_search_behaviour

Correct search behaviour