hello

i want to setup a camel route that has a soap webservice able to receive a
soap message and then route it towards a tcp socket. the tcp socket has to
wait for a client to connect, if its connected it then sends the message
towards it

cxf endpoint --> tcp socket (netty)


i created a cxf endpoint/webservice that normally responds to the message,
and as a test i connect a file/output endpoint to it. This worked as the
contents of the message were put into a newly created file, so far so good i
thought.
Now changing the file endpoint to netty endpoint some problems occured

1. i do testing with socket test 3, when i try to connect to that port as
client it doesnt allow me to connect (maybe because that endpoint is acting
like a client too?)

2. if i just listen on that port, i get the following message "Y sr
*org.apache.cxf.message.MessageContentsListxr java.util.ArrayListxp ..."

now my question

is it possible to have a soap accepting endpoint on one end and a tcp socket
on the other, that accepts connections from a client?






--
View this message in context: 
http://camel.465427.n5.nabble.com/problems-with-route-cxf-netty-tp5744294.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to