The WSDL document is the contract between the server and client. Unless you're using non-standard SOAP types, i.e. passing serialized objects, the client and server language/technology doesn't matter. Passing opaque objects may require the client to be a particular technology and would require the client to know how to deserialize the objects.
So, given just the WSDL file, you should be able to use Java, .Net, Perl, etc, to talk to the server. I commonly use Perl clients to test J2EE and .Net webservices. You should be able to get the WSDL file by tacking "?wsdl" to the end of the web service URL in a browser. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887176#3887176 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887176 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
