For transports that have no GET like semantics there isn't such a simple solution. The WS-MetadataExchange[1] specification defines a protocol for returning WSDL from any endpoint by sending it a "MEX Request" This is just a SOAP message as defined in the spec[1]. You can see how say a TCP or JMS based web service could return its WSDL given an explicit SOAP request to its endpoint for it.
The downside of MEX is that I don't know of any shipping SOAP stack that implements it yet but it is coming. :-(
Regards Jim Murphy
[1] - http://www-106.ibm.com/developerworks/library/specification/ws-mex/
Koney, Satish wrote:
Thanks a lot Mahen,
For Question 3...does it mean that "?wsdl" cannot be used if someone wants strict portability? What are the other ways of getting WSDL?
Question 2 remained unanswered...can ony one plz???
Thanks, SSSS
-----Original Message----- From: Mahen Perera [SMTP:[EMAIL PROTECTED] Sent: Tuesday, October 19, 2004 5:02 PM To: [EMAIL PROTECTED] Subject: Re: 3 questions
Hi SSSS,
Listed some answers,,, not sure on the second Q..
Answers
1) Yes, must go thru the Axis Servlet,, however if u want u can have some filters which get called before the Axis Servlet ..
2) No idea
3) Most of the SOAP engines provide that feature of getting the WSDL using ?wsdl appended to the URL of the service
Mahen
On Tue, 19 Oct 2004 06:23:06 -0400, Koney, Satish <[EMAIL PROTECTED]> wrote:
Hi Guys,
I have 3 questions on usage of AXIS. Plz clarify
1. If the web service is developed in Axis, should all the requests
coming
from the clients go to AxisServlet first? ( which means that the Axis MUST be deployed as one web application in the server)
2. Should the web service be under one web application?. Read somewhere
that
it can be packaged into WSR. But all the servers do not recognise that WSR packaging.
3. If the URL ends with ?wsdl, the WSDL for that service is returned. Is
it
specifict to axis? If it is, then is there any other way to get the
WSDL?
Thanks, SSSS
____________________________________________ Confidential: This electronic message and all contents contain
information
from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If
you
have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.
____________________________________________ Confidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.
