Title: TR: Really a DIIclient in Axis?

hello,

My context : Axis1.2 on windows, WSP and WSC Axis/java
I have a WSP that expose the following operation, returning a Bill type:
   public Bill compute Bill ()

I have defined the Bill type in the wsdd file as following :
<!-- Bill type -->
      <typeMapping
        xmlns:ns="http://endpoints.ws.Fun"
        qname="ns:Bill"
        languageSpecificType="java:MyServices.Bill"
        serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
        deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
        encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      />
My WSP is deployed/runnnig in Axis/tomcat and it is called from an Axis  WSC
Like this….
call.setOperationName("computeBill");
Bill bill = (Bill)call.invoke( new Object[] {} );
…...
Everything is ok , but i want to really have a pure DII WSC approach, without having the client code
knowing the classes and services that will be called and my problem is that i need to declare

QName qnBill= new QName("http://endpoints.ws.Fun", "Bill");
                 call.registerTypeMapping(Bill.class, qnBill,
                                          new BeanSerializerFactory(Bill.class,qnBill),
                                          new BeanDeserializerFactory(Bill.class,qnBill));

at the beginning of the WSC code …
So my question is :
How to develop/code my WSC to don't know  classes at compile time …?

Any idea
Thx
Philippe


Reply via email to