Allow specification of Accept-Type by appending a registered suffix to the request path

[gitblit]

This PR allows specification of the Accept-Type on the Request path.

http://localhost:8338/contact
http://localhost:8338/contact.json
http://localhost:8338/contact.xml
http://localhost:8338/contact.yaml

The path suffix is matched against the trailing pseudo-suffix of the registered ContentTypeEngine.

e.g. application/json = json
e.g. application/x-yaml = yaml

GET("/contact(\\.(json|xml|yaml))?", new RouteHandler() {
    @Override
     public void handle(RouteContext routeContext) {
        Contact contact = new Contact()
            .setId(12345)
            .setName("John")
            .setPhone("0733434435")
            .setAddress("Sunflower Street, No. 6");
        routeContext.xml().negotiateContentType().send(contact);
    }
});

Aside from the verbose route path specification, the behavior is transparent to the end-user. I have an idea on how to make this suffix support easier to use for route registration but it will require some rearchitecting to achieve.

[gitblit]

@decebals I happen to think this change is particularly useful - although the route registration could stand improvement. More on that if we can get this merged.

[decebals]

I think that this feature can be useful for some people.

[decebals]

From implementation I see a permutation: suffixOrContentType instead of contentTypeOrSuffix. Am I wrong?

[decebals]

Thanks

[gitblit]

Cool. Thanks for the merge.

[decebals]

@gitblit Can you update doc with this cool feature, please?