Hi Leena, You can use standard RESTEasy client API to call your RestB within RestA.
I wonder the reason why you don’t want to expose URI in your call. Do you want to bypass all the network overhead? If so you can consider to refactor your RestB and put the common logics into separate APIs that not exposed as a web service. -- Weinan Li On Friday, February 7, 2014 at 3:50 AM, Cassa L wrote: > Hi, > I have two REST interfaces in my web application. say RestA and RestB. RestB > needs to invoke a method from RestA within same container from one of its > method. > > How do I call this? If I try to create ProxyFactory, I need to give URI. Is > there a way to just call this resource without using URI and invoke directly. > All resources are registered with the container when I initialize > application, but cant figure out way to get it. > > Regards, > Leena > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > > _______________________________________________ > Resteasy-users mailing list > Resteasy-users@lists.sourceforge.net > (mailto:Resteasy-users@lists.sourceforge.net) > https://lists.sourceforge.net/lists/listinfo/resteasy-users ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ Resteasy-users mailing list Resteasy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/resteasy-users
