Thanks to all of you for taking time to reply. I've browsed through the CXF library and, true enough, it doesn't have provision for plain socket transport.
The Conduit interface will use the HTTPConduit as default implementation and the EndpointInfo address does not recognize socket:// URI. Same goes with all factory beans. JAXB will have to go directly to OutputStream then. On Thu, Jul 16, 2009 at 2:44 AM, Sergey Beryozkin <[email protected] > wrote: > > It might be useful for restful WebClient, when it needs to support > arbitrary > HTTP verbs, so rather than bundling in Apache HTTP Client it could be much > cheaper just to use a SocketConduit. > > So yes, a patch would be welcomed :-) > > cheers, Sergey > > > dkulp wrote: > > > > On Tue July 14 2009 9:19:33 am Michael Paolo Cariaso wrote: > >> Hi, > >> > >> Is it possible to use CXF to send any message(soap, html in String or > >> byte > >> array) via plain java Socket instead of JAXWS(HTTP)? > >> > >> I've been looking at Conduit Class but I can not find any implementation > >> that will allow it to connect via socket instead of HTTP. > >> > >> Any reply will be appreciated much. Thank you. > > > > I don't think anyone has written one yet. Hasn't really been needed. > > Feel > > free to contribute one. :-) > > > > > > -- > > Daniel Kulp > > [email protected] > > http://www.dankulp.com/blog > > > > > > -- > View this message in context: > http://www.nabble.com/Use-CXF-to-transport-message-Through-Java-Socket-tp24479404p24503668.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
