The messages you show use SOAP encoded arrays. SOAP encoding is not allowed by
the BasicProfile-1.0 and not well supported by WS4EE.
You probably want to migrate your application to rpc/literal or
document/literal style.
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
Thanks for your reply Jason.
I'm not following jbws-349 too well but it doesn't look related. I should have
explained that I have two clients; one that works because it includes the
attribute and one that doesn't.
Bad message
http://schemas.xmlsoap.org/soap/encoding/";>
|
| image
I looked at your code, and i see that you are modifying xsi:type, the
setAttribute is probably working, the problem is that it is improperly ignored,
which would most likely be this bug:
http://jira.jboss.com/jira/browse/JBWS-349
-Jason
View the original post :
http://www.jboss.com/index.html
Thanks Jason. I think that did the trick!
But it looks like the attribute has no effect and I think it's because the XML
has been deserialised once already. So I think when RPCInvocation does
Vector args = body.getParams();
It returns the attributes before the XML was modified. I don't understa
Have you tried using Element.setAttribute(String, String)/getAttribute(String)
instead?
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912778#3912778
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912778
