Basically, the CXF BC with JMS transport is one way that the system is exposed to the outside world. Messages come into the system from a third party via the CXF BC consumer JMS queue. From there, a message flows into a Camel service unit through where it gets routed through a few minor logging routes before being sent into a different queue that is supposed to ensure reliable message delivery in the event of ServiceMix getting disrupted. After being placed on this queue, an ordinary JMS consumer consumes it off the queue to bring it back into the system and sends it on for further processing by various services.
The point where things encounter problems is when this JMS consumer tries to consume the supposedly UTF-8 message produced by the CXF BC consumer. In the logs, the message does appear OK at each step before being taken off the second queue. I see the French accented characters in the message at the proper place and no garbled text. Yet the JMS consumer pulling the message off the second queue complains about the invalid bytes. Freeman-2 wrote: > > Hi, > > I'm a little bit confused with your scenario, could you please explain > your flow? > How could you put message into a ActiveMQ queue through cxf bc > consumer with JMS transport? > Cxf bc consumer with JMS transport would consume message from > queue(but not put message into queue), seems both your cxf bc consumer > and jms consumer consume messasge from same queue(which doesn't make > sense IMHO) , do I miss something? > > Freeman > -- View this message in context: http://servicemix.396122.n5.nabble.com/Character-Encoding-Problems-Using-CXF-Consumer-with-JMS-tp461424p509932.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
