Hi,
I am not sure if this is a bug with the wsdl2Java Axis class or not.
I have generated my Java Stub from a wsdl, but when I try to invoke
a method, the validation fails, complaining that the operation name
is not set.
" No operation name specified!
at org.apache.axis.client.Call.invoke(Call.java:1654)"
This indeed will always be the case, as the generated stub looks like this:
...
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[1]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI("http://localhost/";);
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
setRequestHeaders(_call);
setAttachments(_call);
java.lang.Object _resp = _call.invoke(new java.lang.Object[] {user,
password, recipient, text});
...
NB: _call.setOperation(OperationDesc) is called and not
_call.setOperation(String) or _call.setOperation(OPName, String) that would
set the operationName on the _call object.
Does Call.setOperation(OperationDesc) require the similar logic to
Call.setOperation(String) whereby the operation name is set as well
viz:
public void setOperation(String opName) {
if ( service == null )
throw new JAXRPCException( Messages.getMessage("noService04") );
// remove all settings concerning an operation
// leave portName and targetEndPoint as they are
this.setOperationName( opName );
....
Or does wsdl2Java call the wrong method on Call?
Or have I left something out?
Cheers,
Nick
>-----Ursprungliche Nachricht-----
>Von: Charles Roy [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 3. August 2004 17:27
>An: [EMAIL PROTECTED]
>Betreff: What does streaming=on do for server message processing?
>
>
>Hi,
>
>I was wondering what the "streaming=on" attribute in the WSDD for a RPC
>service does for Axis 1.1 as compared to 1.2?
>
>Does it setting streaming=on prevent the creation of the serialized
>return message being stored in a string and/or buffer by Axis on the
>server before it is output to the client?
>
>Thanks,
>Charles
>
>
>
