Ron thx for the detail reply.. I think is prob to do with one. For some reason during the upgrade I removed the @Produces stuff from the service class.. I am gonna add it back in and see how it goes..
Great to see CXF's mailing list is so helpful :)) Charlie 2009/2/22 Christian Schneider <[email protected]> > Benson Margulies schrieb: > >> OK, I'm confused. >> >> The non-xml log files look fine to me when I just read them into an >> editor. >> >> Wireshark says 'invalid text', but it mostly it is just truncating. I >> see <ns2:id><ns2:com, and then it stops. It looks more like the server >> truncated than that anyone injected trash. I see this with the 'follow >> TCP stream' option which dumps the entire session. >> >> What we're really crying here is for a way to make a CXF client reject >> this. There's nothing on our client side that would paper-over junk in >> the stream. >> >> >> > > Sometime ago I had a problem with CXF and truncated xml. It happened when I > turned on the logging interceptor. > When the logging was on the xml was truncated when it was off it was ok. > Perhaps this could be something similar. > > Greetings > > Christian > > -- > > Christian Schneider > --- > http://www.liquid-reality.de > > -- http://finker.wordpress.com/
