Hi Bill,
Sure, please log the Jira.
Just to be clear - what you suggest is adding new method that would be "safe", not changing behavior of the existing method that is enforced by TCK, right?
Marek
On Jul 15, 2013, at 2:54 PM, Bill Burke <bburke_at_redhat.com> wrote:
> UriBuilder path(Class resource, String method);
>
> IMO, this method should do nothing if there is a a http method annotation on the Java method. Right now, the method throws an exception if no @Path is on the Java method. (I think the TCK tests this too).
>
> The case would be this:
>
> @Path("/root")
> public class Foo {
>
> @GET
> public String get() {}
> }
>
>
> uriBuilder.path(Foo.class).path(Foo.class, "get").build();
>
>
> This points to the java method you want and ensures that if a @Path is added in the future to the get() method, the appropriate path gets generated still.
>
> If you agree I'll log a jira.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com