custom transport

[Fazle Khan <fa...@gmail.com>]

we are using a 3rd party transport that I'd like to develop a contract first
xml service against.  The 3rd party app deploys it's own servlet and
supplies the xml messages to our code via a call-back object we implement. 
I could use Xstream to get the request and route requests based on the xml
but I'd like to develop this as a contract first service.  How hard is it to
write my own custom transport that takes in xml strings and routes to
different endpoints? 
-- 
View this message in context: http://www.nabble.com/custom-transport-tp17260625p17260625.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: custom transport

[Willem Jiang <wi...@gmail.com>]

You can find a relate thread[1] in cxf dev list.
I think we could add a wiki page for this popular topic :)

 From you use case description , I think you could take a look at 
Camel[2]which could help you to do the content base routing thing.

[1] http://www.nabble.com/Writing-my-own-transport-td17088528.html#a17088528
[2] http://cwiki.apache.org/CAMEL


Willem

Fazle Khan wrote:
> we are using a 3rd party transport that I'd like to develop a contract first
> xml service against.  The 3rd party app deploys it's own servlet and
> supplies the xml messages to our code via a call-back object we implement. 
> I could use Xstream to get the request and route requests based on the xml
> but I'd like to develop this as a contract first service.  How hard is it to
> write my own custom transport that takes in xml strings and routes to
> different endpoints? 
>