Hi all,

I've submitted issue RESTEASY-772 but I've been told I should post my problem here instead, so here goes:


I have the following (dumbed down) interfaces:

@Path("root")
public interface Root{
   @Path("sub") SubResource subResource();
}

public interface SubResource{
   @GET get();
}


This thing works properly on the server side: calls to root/sub/ are properly sent to the exposed SubResource implementation. However, this doesn't work with the client framework: the client instead sends the request to sub/. It seems like it ignores the @Path("root") on the root resource definition.

I've looked in the codebase and the SubResourceInvoker indeed doesn't have that information when building its uri. This is kind of a blocker for me since it means I can't use the same interface for the server and client. Is there a known way to make this work?
--
Pascal GĂ©linas | Software Developer
*Nu Echo Inc. *
1435, Saint-Alexandre, Suite 200, Montreal (Qc),Canada, H3A 2G4
Tel: (514) 861-3246 ext 4234 | FAX: (514) 861-1676
pascal.geli...@nuecho.com <mailto:pascal.geli...@nuecho.com> | www.nuecho.com <http://www.nuecho.com/> | blog.nuecho.com <http://blog.nuecho.com/>

*Because performance matters. *
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Resteasy-users mailing list
Resteasy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/resteasy-users

Reply via email to