Brad, I've made some changes to make sure we try and map any charset values that are passed in into the canonical forms the parser may expect. The result is that in your case, the ENCODING does get set to UTF-8 on the message instead of utf-8. Hopefully that solves the problem.
I'll try to deploy a new snapshot sometime this weekend. (hopefully tonight actually) Dan On Friday 21 September 2007, Daniel Kulp wrote: > Brad, > > Are you sure you are using woodstox 3.2.1 as the Stax parser? I > traced through the woodstox code and the first thing it does is > convert utf-8 to UTF-8. Thus, I'm not sure how it could possibly be > causing an issue. Still digging though.... > > 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
