Hi

During the last couple of weeks I've had a chance to gradually update the
CXF JAX-RS docs.
I haven't done it since January - I'm really at fault here. I've fallen into
the trap of thinking that I could do/code something else and then a bit
later will update the docs...

I've tried to update everything related to what I may've replied to or have
worked upon during the time since January till March...

This includes :
- how to configure RequestDispatcherProvider to redirect to a JSP engine
with CXF servlet listening on "/"
- completing the section on the Atom logging (pull style) (this will need to
be moved into a CXF Logging page as this feature is available to
jaxws/jaxrs) and which Tomasz may need for his work
- updates on how to configure JAXB/JSON in/out transformers, to do with
wildcards
- WebClient/proxy thread safety
- Multipart/XOP support
- Getting messaged over JMS
- fast infoset
- Atom (AtomPojoProvider)
- Customizing WADLGenerator, initial effort for supporting the external
schemas
- minor updates to XMLSource
- generating & downloading client test code at runtime
- advanced search capabilities (SearchContext and SearchCondition -
available at 2.3-SNAPSHOT only given that Atom ReadableStorage depends on it
and thus there might be some changes till 2.3 gets released)

this is probably it. I haven't mentioned JMX as at the moment nothing
JAXRS-specific can be displayed, though the response counters should work
well even if multiple root resources are involved.

As I've mentioned earlier on, the pace of development will most likely slow
down significantly, provided things will work out the way I'm expecting them
to. We have two interesting GSOC projects approved for CXF involving JAXRS
so it will be a real community contribution once they are finished. As far
as I'm concerned, I'll be looking into fixing bugs, spend some time with
investigating a Jettison issue in DOSGi RI before 1.2 is released, start
evaluating how 1.1 compliance can be achieved, plus explore what other
extensions can be done (security, client api, etc) - on my own time. I guess
CXF JAXRS will move forward as fast as a turtle :-) (the phrase I've learnt
recently) but it will move...

Sergey

[1] http://cxf.apache.org/docs/jax-rs.html

Reply via email to