Hi David, Thanks for the reply.
I have hit the WADL address. I could only see /content/. Cant find out /detail/. One question: Is it mandatory that, I need to pass all the queryparams in the URL. Because, when I removed all the parameters from the getLocalDetail method signature, it works. I guess, there is something wrong with the way QueryParams are used. Thanks & Regards, Yong-Loh KARR, DAVID (ATTCINW) wrote: > >> -----Original Message----- >> From: Yong-Loh [mailto:[email protected]] >> Sent: Wednesday, January 27, 2010 8:15 PM >> To: [email protected] >> Subject: CXF with JAX-RS : No operation matching request path /detail/ >> is found >> >> >> Hi All, >> >> We are using CXF with JAX-RS for building RESTful webservices. Below > is >> our >> resource interface. >> >> @Path("/") >> public interface ContentProcess { >> >> @GET >> @Path("/content/") >> @Produces("application/xml") >> public Content getContent(@QueryParam("address") String address); >> >> >> @GET >> @Path("/detail/") >> @Produces("application/xml") >> public Content getLocalDetail(@QueryParam("address") String >> address, >> @QueryParam("region") String region, >> @QueryParam("effectiveDate") String effectiveDate); >> } > > It's always a good idea to hit the WADL address, which might be > "/ServiceLayer?_wadl". That will list the resource paths that are > expected. > > I would imagine that having your server address as "/" and the root path > for the controller as "/" are oddities that might be causing trouble. > If that WADL address produces something useful, you can verify what > paths are really expected. > > > -- View this message in context: http://old.nabble.com/CXF-with-JAX-RS-%3A-No-operation-matching-request-path--detail--is-found-tp27350904p27351652.html Sent from the cxf-user mailing list archive at Nabble.com.
