util for viewing required SOAP request!!

[Krishnendu Kunti]

Hi Guys   If axis has support for viewing a sample soap request for any deployed web service then at the client side the request body can be created (a document style WS client). Does axis (for that any WS platform) incorporate the feature to view the exact required SOAP request for a deployed WS??. I mean WSDL is there for the same purpose..but at times there are not easy.   Cheers Krish   -----Original Message----- From: Yakulis, Ross (Ross) [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 8:13 AM To: [EMAIL PROTECTED] Subject: RE: Need suggestions on web service interop and design   I have made that work with Axis 1.1 where the servce side was created using .net and that wsdl was used to create the Axis and Systinet Java clients.   As I remember it was not completely straight forward but ended up working.  You needed to use basic types int, string, boolean and arrays of simple beans seemed to work as well.  The url to the service had to be massaged to get the generate axis code to work.       public boolean getTrue() throws java.rmi.RemoteException;     public void sendInt(int x) throws java.rmi.RemoteException;     public ArrayOfInfo getInfos(javax.xml.rpc.holders.IntHolder numInfo) throws java.rmi.RemoteException;     public boolean setInfo(Info info) throws java.rmi.RemoteException;   Where Info is   public class Info implements java.io.Serializable {     private java.lang.String first;     private java.lang.String last;     private java.lang.String number;     private java.lang.String description;     ...     ... // appropriate getters and setters adn constructor.     ... }     Ross     -----Original Message----- From: David Thielen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 6:55 PM To: [EMAIL PROTECTED] Subject: RE: Need suggestions on web service interop and design Hi;   What happens if you come from the .net side? We have to make some java code a web service that both .net and java can hit. But what if I create a C# class that models the interface. Then use .net to create the WSDL?   Then… use that WSDL to create the java server and client code? Would that provide an automated method to create everything that generates correct WSDL and source for document/literal?   Thanks – dave   Ps – I’m new to this mail list but the discussion on this topic today has been fantastic – thank you