Changing the binding style to 'DOCUMENT' and parameterstyle to 'BARE' does
away with the above error. But now all the parameters are passed as 'nabble'. Any remedy for
this :ninja:
jaki wrote:
>
> Ok I have decided to ditch the hashmap and he
Element.java:236)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2448)
... 3 more
jaki wrote:
>
> Is your msg incomplete? Cuz it says part of the message was removed to
> comply with nabble security policy.
> If it's n
ay list will work i.e
> ArrayList ret3 = (ArrayList) cu.call.invoke( new Object [] { jobid });
>
>
>
> - Original Message
> From: sarika pramod <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Monday, August 18, 2008 3:31:57 PM
> Subject: Re:
Any help on this? :( I have exposed the ejbs using @Webservice annotations
and not using the axis wsdd method. Should that be what's causing the
problem? Please help
jaki wrote:
>
> Hi all,
>
> I have an axis WS client calling a remote ejb3 web service as below:
>
>
Hi all,
I have an axis WS client calling a remote ejb3 web service as below:
Call call= (Call) service.createCall();
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName(new QName("http://session.um.com/";
