[jax-rs-spec users] [jsr339-experts] Re: Re: Matching algorithm doesn't recurse back on Locators

From: Bill Burke <>
Date: Mon, 20 May 2013 09:40:58 -0400

On 5/20/2013 9:23 AM, Santiago Pericas-Geertsen wrote:
> Yes, I thought the original example was the other way around, but I agree with this one. I think this was an unfortunate copy/paste error in the definition of M (from earlier in step 2). It should be,
> M = { subresource methods of all classes in C′ where R(T_method) = R_match (excluding sub-resource locators) }
> which should result in M = \empty and no jump to step 3.
> Make sense?

There's still other holes (see my previous email). Additionally , what
about this case?

public class Resource {

    public String get() {...}

    public Locator locator() {...}


public class Locator {

     public String get() {...}



GET /sub
Accept: application/json

I have a regression test for this in Resteasy from a bug that a user
reported of this very case. Depending on my TCK challenges, I'm not
sure yet whether I'll be able to support this case going forward.


Bill Burke
JBoss, a division of Red Hat