From: Bill Burke <bburke_at_redhat.com>
Date: Tue, 18 Mar 2014 12:38:57 -0400

Yet another user complaining about the JAX-RS matching algorithm...

Enjoy! More to follow :)


-------- Original Message --------
Subject: [Resteasy-developers] Upgrading from 2.3.3 to 3.0.6
Date: Tue, 18 Mar 2014 11:34:30 -0400
From: XXXXXX
To: resteasy-developers_at_lists.sourceforge.net


Hello,

We're attempting to move from 2.3.3 (final) to 3.0.6 (final) and
experiencing a few issues. One is an apparent change to the matching
algorithm - for example, we have...

@Path("path")
public interface Resource
{
   @Path("subresource/{id}")
   SubResource get(@PathParam("id") String id);

   @PUT
   @Path("subresource/{id}")
    String open(@PathParam("id") String id);
}

public interface SubResource
{
   @DELETE
   String close();
}

Previously that would work fine. Now we get an exception / 405 code
because it finds the PUT (only/instead). If I comment out the PUT, then
the DELETE gets called fine. What is the best way to address this?

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com