bugfix aligning service names

[K-Jo]

There is a difference in the substraction of service names in between implementations. If a service "a" gets called without span information in the headers, the brave pre processor would name the service "/a" because of the javadocs: http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getContextPath(). The client as a counterpart takes a subpart https://github.com/kristofa/brave/blob/master/brave-client/src/main/java/com/github/kristofa/brave/client/ClientRequestInterceptor.java getServiceName

[kristofa]

Hey, Indeed service names for client and server endpoints should be same. See pull request #19 .
Now we can have inconsistencies between implementations (RestEasy, Jersey,...) because on server side each implementation has its own logic for submitting end point and specifying service name. If there would be a brave-server module similar as has been done with client, see #27 , this would get aligned and we would avoid code duplication.

But your change should fix RestEasy implementation. Thanks!

[kristofa]

This pull request made it into brave version 2.3 which should appear shortly in Maven Central.