This content has been marked as final.
Show 2 replies
-
1. Re: Unexpected encoding style
thomas.diesler Apr 22, 2005 4:34 AM (in response to platinumdragon)Your client expects the message to be soap encoded. What is actually beeing sent is literal encoded (the encoding URI is an empty string)
The BasicProfile-1.0 prohibits soap encoding. JBossWS, which must be BP-1.0 compliant does not support it therefore.
You should instruct your client to use literal encoding. -
2. Re: Unexpected encoding style
platinumdragon Apr 22, 2005 2:30 PM (in response to platinumdragon)Ah yes, thank you.
I was using the wscompile -f:rpcliteral flag with the server, but not the client. Once I added that, it got past that error.
Thanks,
Mike