It's probably better to do the "encoding" changes whereever we create the XML parser. Probably in the "StaxInInterceptor.java". That way, if some other transport is uses and the same encoding issue happens there, the same fix would apply.
Dan On Wednesday 19 September 2007, Brad Harper wrote: > We're doing testing from different soap clients and have narrowed down > a discrepancy in our responses based on sending in "charset=utf-8" vs > "charset=UTF-8". The native PHP soap client passes in the former and > the namespacing on the child nodes is missing when the lowercase > charset is passed in. Any ideas? > > A semi-hacky solution is adding a toUpperCase() to the character > encoding in ServletController:228... > > inMessage.put(Message.ENCODING, enc.toUpperCase()); > > Figured you guys could tell me if this could cause any adverse > results... > > > Regards, > Brad -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
