Hi Sergey,
If you use exchange to get to one of the message properties inside the
application code then I believe you can use JAXWS WebServiceContext and
CXF JAX-RS MessageContext extension...
That is exactly the work-around I mentioned. However, it would be nice
if I could reduce it to j
Hi,
Yes, I meant the actual resource class. I have not read the spec, so I did
not know that this was the case. I just wanted to give you a heads up in
case this was an actual bug. It's not that hard to copy the path into each
methods @Path-annotation.
Cheers,
Christoffer
Sergey Beryozkin-2 wr
Hi
> @Path-annotation
supposed to work when used on a sub-resource class
do you mean the one the actual resource class ?
No, when resource classes act as sub-resources then root Path
annotations are not taken into account per the spec. May be we can add a
configuration option to bypass this rest
Thanks a lot, this really helped! I had not noticed the fact that it was
possible to return Objects. A small question though: is the @Path-annotation
supposed to work when used on a sub-resource class? I cant seem to get it to
work. It however works perfectly when annotating methods in that
sub-re
Hi,
I'm trying to get my RESTful web service methods to work, but I keep getting
these errors:
Jun 7, 2009 1:07:27 PM org.apache.cxf.jaxrs.utils.JAXRSUtils
readFromMessageBody
WARNING: .No message body reader found for request class : User, ContentType
: application/xml.
Jun 7, 2009 1:07:27 PM
o
