I'm afraid I've got confused. The proxies (created from interfaces or concrete classes) are just proxies. The only reason the proxies for the concrete classes are supported is to cover the case when for whatever reasons one can not use interfaces or WebClient.
The concrete JAXRS resource class may have many methods, some of them are real JAXRS resource methods and some not but as far as the proxies to those classes are concerned they expect that the methods being invoked are the JAXRS methods, what else they can do with non-'complying' methods but throw the exception ? cheers, Sergey On Wed, Jul 21, 2010 at 2:38 PM, cxfJim <[email protected]> wrote: > > Oh, I am sorry, I forgot to mention, when the exception happens: It is > thrown > everytime I call any method which is part of the implementing class, > whether > it is a service method or not > -- > View this message in context: > http://cxf.547215.n5.nabble.com/JAXRS-Initializing-Service-Proxy-through-implementation-class-tp1627376p1719490.html > Sent from the cxf-user mailing list archive at Nabble.com. >
