Hi Sergey,

Well done! :D

Some very minor things I noticed while studying:

1. Under "Filters" :

InputStream is = message.getContent(InputStream.class);
message.setContent(new MyFilterInputStream(is));
message.put(*m.put(*Message.ACCEPT_CONTENT_TYPE, "custom/media");

The "m" is not a declared variable and the parentheses doesn't add up.

2. Under "Dealing with contexts", just before "JAX-RS and Spring AOP":
@WebMethod public void doItSoap(String b) { isUserInRole(jaxwsContext.getSecurityContext().getPrincipal()); }; @POST public void *doItSoap*(String b) { isUserInRole(jaxrsContext.getSecurityContext().getPrincipal()); }

doItSoap -> doItRest, ryt?

Hth.

Gabo

Arul Dhesiaseelan wrote:
Sergey,

Well documented.
I had couple minor issues when I was going through the doc.

The doc does not refer to the CXF-2.2-SNAPSHOT maven repo (http://people.apache.org/repo/m2-snapshot-repository). Its easy to locate though, but may be handy for users trying to build using 2.2 snapshots.
The other one is a typo which reads:

The wire representation of Customer object is:
@Path("/customerservice/")
<Customer>
    <id>123</id>
    <name>John</name>
</Customer>

I think @Path referenced is a typo, right?

Does JAXRS frontend support multiparts yet? Just curious to know about the plans.
Br,
Arul

----- Original Message -----
From: Sergey Beryozkin
[mailto:[email protected]]
To: [email protected]
Sent: Wed, 24 Dec
2008 11:38:12 -0700
Subject: JAXRS documentation


Hi,

I've worked today on updating the CXF JAXRS documentation.
Please review it. Feedback will be welcomed - please contact me directly
or reply to this email. If you thing anything obvious is missing or
needs to be further expanded upon, let me know please.
Merry Christmas to everyone

Cheers, Sergey

[1] http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html

------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM

Reply via email to