A simple testcase for this would be great if at all possible. I just tested this by adding the string "john&marry" to the testString stuff in our type tests and it passed fine. The full string was properly echoed back. Thus, I'm not sure what would be going on. A test case would definitely be useful.
Dan On Fri May 1 2009 3:38:44 am marcob wrote: > That was my first reaction as well! > Yes, I have CXF at both ends. I don't know if it might help, but in the > previous post I forgot to say that my WS stack also includes a WS Security > Interceptor. When I come back to the office (Monday), I'll test the same > code without WS-Security and check whether exists a more updated version of > woodstox library. > In the meanwhile, any further suggestion is very welcome! > Marco > > bimargulies wrote: > > My first reaction is that I don't believe it. It is the woodstox code > > that handles all of this, not us. Is the CXF on both ends? > > > > On Thu, Apr 30, 2009 at 12:21 PM, marcob <[email protected]> wrote: > >> Hi, > >> > >> I've found this unexpected behaviour while using cxf 2.2.x + JaxWS + > >> Aegis. > >> If I define a method that accepts string parameters, e.g. > >> > >> public void echo(String text) { > >> System.out.println(text); > >> } > >> > >> and I pass a string containing the ampersand character (&), e.g. > >> "john&lucy", the echo method only prints "john". I investigated the > >> problem > >> with an HTTP Monitor and it seems that at client side the string is > >> correctly escaped (the SOAP request contains the "john&amp;lucy" > >> text) > >> but, at server side, the string is truncated at the & character > >> position. > >> > >> From my point of view, it seems to be a bug. > >> Any solution? > >> Thanks > >> Marco > >> -- > >> View this message in context: > >> http://www.nabble.com/CXF-2.2.x-ampersand-issue-tp23319655p23319655.html > >> Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
