Title: Axis - Castor Issues

Hi,

In my project, we intend to use Axis 1.1 with Castor to develop and deploy web services. We were doing some prototyping with Axis & Castor, but ran into a few issues which we need to solve before we can go ahead. Kindly find the details below and let me know if there are any solutions for any of the mentioned issues.


Requirement

To setup a single Web service with four operations (CRUD), listening on a Axis engine

Development environment being used

Windows XP, WSAD 5.0, Apache Axis 1.1, Castor-0.9.5.2

Procedure Followed

Firstly, we integrated WSAD with Axis. Developed WSDL and XSD files and provided them as input to Axis’ WSDL2java tool. To integrate Axis with Castor for data binding, made the necessary changes to accommodate Castor serializers and deserializers in the Stub and deploy.wsdd , and then deployed the service in the WSAD Test environment

Major Issue being faced

§       Axis’ Document type web service support is immature. Incorrect method invocation seems to take place while using document style in WSDL. We deployed a web service with updateOperatorProfile() and  createOperatorProfile() methods. Through a Test client, when we invoked updateOperatorProfile(), somehow the createOperatorProfile() was being invoked instead of updateOperatorProfile(). On investigation, the reason for this seems to be that the operation to be invoked is NOT selected on the basis of ‘qname of the operation’ but selected on the basis of ‘qname of input parameters’. As for these two methods the input parameter is same (also having same qname), the operation which is defined first in the descriptor file gets invoked by default.


Other Issues Faced :

§       Axis generated stub and deploy.wsdd contains stray elements and characters and this used to cause errors at runtime. In the stub constructor,  when a QName was being instantiated, we found a “>” character just before the element name. In the deploy.wsdd, we found a “>” character in the value of the qname attribute of the <typeMapping> element.  

§       Castor does not generate Java classes for <xsd:simpleType/> present in the XML schemas, only Axis does. Looks like Castor does not have support in terms of serializers/deserializers for <xsd:simpleType/>

§       Data Binding classes generated by Axis and Castor for the same XML schema have different names and this creates confusion. Axis generated class names start with a underscore character(for eg _AdminGroups) whereas Castor generated files do not start with underscore (AdminGroups)

§       Both Axis and Castor (for XML <simpleType> and <complexType> respectively) generated data types needed to be used for serializing & deserializing types and this adds to the confusion


What we are looking for

    §       Robust support by Axis for document style web services

    §       Any suggestions or guidelines for a better integration experience between Axis and Castor



Regards,

Manoj Nandakumar

--------------------------------------------------

Fidelity Information Systems Company India Pvt. Ltd.

1st Floor, Tower B, DLF Center Court

DLF City, Phase-V

Gurgaon HY 122002

Phone: (0124) 502 1648


"Any comments or statements made in this email are not necessarily those of FISC India Pvt. Ltd. or any of the Fidelity Investments group companies. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  If you have received this in error, please contact the sender and delete the material from any computer.  All e-mails sent from or to FISC India Pvt. Ltd. may be subject to our monitoring procedures"



Reply via email to