cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Mao <>
Subject Re: svn commit: r467080 [1/2] - in /incubator/cxf/trunk/rt: bindings/ bindings/http/ bindings/http/src/ bindings/http/src/main/ bindings/http/src/main/java/ bindings/http/src/main/java/org/ bindings/http/src/main/java/org/apache/ bindings/http/src/main/jav...
Date Wed, 25 Oct 2006 03:39:05 GMT
Hi Dan,

What's the 'HTTP binding' for? is it just for REST?
If so why call it 'HTTP binding'? can we call it 'REST binding'?
'HTTP' sounds just like a transport.
The 'HTTP binding' is use HTTP transport, right? so we have 'HTTP over 
HTTP'? sounds weird.

Another question is that current  CXF REST support is  based on  JAX-WS, 
why we need the 'HTTP binding' to expose the JAX-WS service again?

> Author: dandiep
> Date: Mon Oct 23 11:52:16 2006
> New Revision: 467080
> URL:
> Log:
> Add an "HTTP binding" which uses the Java Rest Annotations (new project at the
> Codehaus which James Strachan and I started) to expose JAX-WS services as REST 
> style services. 
> Thanks to Guillaume Nodet who supplied the IriDecoderHelper class which was
> indispensible.
> Currently this just includes:
> o simple server side functionality to take JAX-WS operations and expose them
>   as resources using the @HttpResource annotation and @Get/@Put/@Post/@Delete.
> o Ability to take URI parameters and construct an incoming XML document
>   according to WSDL 2 spec
> o Ability to take URI parameters and an incoming XML document and merge them
> Other things in this commit:
> o Fixed the JAXBDataBinding so we didn't twice initialize the Types if the 
>   WSDLServiceBuilder already did it.
> o Added support for recognizing unwrapped operations in XMLOutInterceptor

View raw message