The bytes message still contains just text. The only difference to text
messages in that case is that it needs to specify an encoding (like UTF-8).
As far as I know CXF can not handle text messages well as it internally
also uses an InputStream.
So I think it is not easy to change that and I think you do not need to
change it.
Christian
Am 18.03.2012 18:04, schrieb Chris Odom:
I created a simple transport for my cxf jax-ws client which is backed with
jaxb bindings. I noticed that when I put the request out on the jms
transport the message body is treated as a bytes message. I wish to
decouple the data format for my messaging system, as in, there will be
services that may or may not use jaxb or, if at all, will even know what a
jaxb context is, I just want them to receive text. With that said is there
an easy configuration maybe in the cxf-codegen-plugin, or cxf client
endpoint parameter for this or do I really have to create camel marshallers
and unmarshallers?
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
