Hi, I'm a new user of Axis and am using Axis 1.1 which is integrated into JBoss 3.2.2 RC1.
>From what I understand, I should be able to take an existing WSDL and use it to generate client stub and server skeleton code using WSDL2Java. Then all I need to do is fill in the implementation class generated by WSDL2Java, compile and deploy the web service using the deploy.wsdd generated. However, when I use the client stubs in a test program the input parameters appear to be null. Here are the steps in order to arrive at this problem: Took a WSDL from a web service written in Microsoft .NET. Here is the WSDL file - (See attached file: TTSysServices.asmx) Using WSDL2Java, I generated the client stubs and server skeleton. I implemented two methods in the implementation class for testing purposes. I then wrote a test program using the client stub. Here is the test program I wrote - (See attached file: TTSysServicesTest.java) Compiled the client stub, server skeleton and test program. Created a WSR file for deployment. The WSR contains the compiled skeleton code, supporting bean classes and this WSDD file - (See attached file: deploy.wsdd) When I run the test program, the first two arguments of the login method of the web service are null. Here is a trace of the request and reply according to tcpmon - (See attached file: request3) Am I missing a step here? I also tried creating a client using Visual Studio .NET 2003 but this time I get a different error. The error I get is a no such operation 'userID' which is the name of the first parameter of the web service method being called. Here is the trace of the request and reply for this - (See attached file: request4) Can Axis interoperate with Microsoft .NET or are there special settings I need to perform? I would appreciate any replies because I am running out of ideas on this and I do not have unlimited time to complete my project. Thanks in advance, Leo
TTSysServices.asmx
Description: Binary data
TTSysServicesTest.java
Description: Binary data
deploy.wsdd
Description: Binary data
request3
Description: Binary data
request4
Description: Binary data
