"the server is rejecting your input" Yes I think so... "I was perplexed by the presence of <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> for no apparent reason." What problems can occur because of that, I was also wondering about that line.
I tried to see what I have on the wire but as long as the message is GZIPped I cannot understand anything, maybe I do not know what to search for... please give me some recommendations where to search for the reason for the problem. P.S. As I said in my first message if I add in the PlaceBetsReqArray one or two PlaceBets everything is working fine but when I add three or more PlaceBets I am getting the exception. bimargulies wrote: > > Roughly, it looks to me as if the server is rejecting your input and > then CXF is having trouble with the fault message. In particular, the > 'illegal char' error is trying to process the fault. > > I had a quick look at the WSDL, and I was perplexed by the presence of > "<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>" > for no apparent reason. > > However, before watching the wire, how about just turned on CXF > logging and seeing what messages are going back and forth? > > > On Wed, Nov 4, 2009 at 6:44 PM, vlaladim <[email protected]> wrote: >> >> "Are you just using a CXF client to talk to someone else's service?" >> Yes, I am using CXF to talk to the betfair service, the wsdl url is in my >> previous message. >> >> "It would be interesting to intercept the request and response using >> TCPMon >> or Wireshark." >> I will try to do that tomorrow, but I am pretty sure that the problem is >> on >> my (client) side and that some illegal characters are messing the things >> up. >> If you give me some recommendation which CXF classes to debug and what to >> search for I will do that... >> >> Want to mention here that I am using the latest version of Ubuntu, I am >> thinking to test that thing under Windows also, do you think that the >> reason >> can be in the OS? >> >> Vlad >> >> >> That doesn't look like a character encoding problem, but more like a >> problem with chunked encoding at the HTTP level. It would be >> interesting to intercept the request and response using TCPMon or >> Wireshark. >> >> Andreas >> >> On Wed, Nov 4, 2009 at 19:13, Benson Margulies <[email protected]> >> wrote: >>> Um, now I'm more confused than before. >>> >>> Are you just using a CXF client to talk to someone else's service? >>> >>> The indications here are someone or something is confused about using >>> UTF-8 (or not) as the character encoding, or else you have a very >>> picky schema. >>> >>> >> -- >> View this message in context: >> http://old.nabble.com/Problem-with-illegal-characters-I-guess...-tp26195769p26206627.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://old.nabble.com/Problem-with-illegal-characters-I-guess...-tp26195769p26219831.html Sent from the cxf-user mailing list archive at Nabble.com.
