Re: [JAX-RS][Sub-resource locator] No operation matching request

[Gabo Manuel]

Hi Sergey,

I opted for the previous suggetsion. The thought entered my mind on my 
trip home yesterday.

 @Path("/Account/{uniqueId}")
  public Account getAccountProperty(@PathParam("uniqueId")   long 
uniqueId) {
       return getAccount();
 }

Although I modified it to have that additional '/' at the end of the 
path. Just to make sure. I don't think the extra method is that cumbersome.

Again, my thanks for your help. :)

Gabo

Sergey Beryozkin wrote:
Anoter option is to introduce a cxf-specific extension which would 
allow the same method be treated as either a resource method or a 
subresource locator method. It won't interoperate between JAX-RS 
impls, but it would let users to save on creating a new method - which 
might be not that easy on a more controlled environments - like this 
is the 3rd part interface we use and we can't change it type of 
requirements. The choice will up to a user (enable this feature or not 
- disabled by default)

Cheers, Sergey

Hi Gabo

Will this work for you :
class AccountService() {
  @GET
  @Path("/Account/{uniqueId}")
   public Account get(@PathParam("uniqueId")   long uniqueId) {
        return getAccount();
  }

  @Path("/Account/{uniqueId}")
   public Account getAccountProperty(@PathParam("uniqueId")   long 
uniqueId) {
        return getAccount();
  }

}