Don't assume that all that happens happens just with the code present in the skeleton or stub code which we see. Tweak a configuration for example the return type QName's namespace in server-config.wsdd and rehost the service and see what you get on the tcpmon as the server response.
Thanks
Jaya
On 12/13/05, Bengali Bengali <[EMAIL PROTECTED]> wrote:
Hi,
I don't really understand what's the point of having an <operation> element in the server-config.wsdd .
Actually, I generated my Axis stubs and skeletons from the WSDL2Java utility.
The prefixes in the SOAP request and response are not what I expected and I wanted
to tweak them in the <operation> element of the server-config.wsdd.
But when I have a look at the generated stub and skeleton of my web Service
I see static initialization of operation description like this (extract of the skeleton):
static {
_operations = new org.apache.axis.description.OperationDesc[1];
_initOperationDesc1();
}
private static void _initOperationDesc1(){
org.apache.axis.description.OperationDesc oper;
org.apache.axis.description.ParameterDesc param;
oper = new org.apache.axis.description.OperationDesc();
oper.setName("call");
param = new org.apache.axis.description.ParameterDesc (new javax.xml.namespace.QName("http://www.mycompany.com", "CallRq"), org.apache.axis.description.ParameterDesc.IN , new javax.xml.namespace.QName("http://www.mycompany.com ", "CallRqType"), com.fis.infra.webservices.model.CallRqType.class, false, false);
oper.addParameter (param);
oper.setReturnType(new javax.xml.namespace.QName(" http://www.mycompany.com", "CallRsType"));
oper.setReturnClass(com.fis.infra.webservices.model.CallRsType.class );
...}
So i don't really understand what's the point of <operation> element ?
Can anyone enlight me ?
Thanks in advance,
Luc
--
-- Jaya
