But it's worth mentioning that this is not a JAX-WS RI bug either, plain JAX-WS RI Dispatchers seems to work ok. I couldn't find the exact source of this strange behavior, the very presence of CXF in the classpath doesn't cause it. I suspect the cause to be that in my application i used both Dispatchers (created by java code using API, therefore they were JAX-WS RI) and Providers (created using CXF spring config) and these two were used together to form a WS Proxy like service - Provider got a message, enriched it and sent it out through the Dispatcher. Maybe this could be the problem or maybe not ;-)
On Fri, Nov 19, 2010 at 3:25 PM, Daniel Kulp <[email protected]> wrote: > On Friday 19 November 2010 7:36:59 am Peter Mihalik wrote: > > Pls. ignore the message. The problem wasn't with CXF. I was deploying the > > client to a Glassfish server and the CXF libs got overridden by the > JAX-WS > > RI libs contained in the app server. After setting the classloader to > > delegate=false the problem disappeared. > > Wow. Good to know. Kind of surprising, but thanks for the update. > > Dan > > > > On Fri, Nov 19, 2010 at 12:20 PM, Peter Mihalik <[email protected]> > wrote: > > > Hi, i'm trying to call a ws using the JAX-WS Dispatcher API as > described > > > on http://cxf.apache.org/docs/jax-ws-dispatch-api.html, but when i try > > > to send some data containing unicode characters (for example 'ľ', 'š', > > > 'č') what's actually sent is: 'ľšč' am i missing somethnig? > > > > > > Thanx > > > > > > -- > > > Peter > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog >
