RE: Turning off ?wsdl feature

Wed, 02 Apr 2003 13:45:27 -0800

Title: Message
Mike, I believe I understand what you mean now. The <wsdlFile> entry can be replace with a URL, so it doesn't necessarily have to be a physical resource such as a file. I will have to give that a shot to see if it works. I probably have to give it an absolute URL for it work, though. Is this what you meant?
-----Original Message-----
From: Mike Burati [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:44 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Turning off ?wsdl feature

You lost me - not sure why you'd want it to be /axis*?wsdl...
 
The article describes how in the WSDD deployment descriptor, you would go about changing the URL used for that service, for retrieving WSDL.  That URL can be a resource in your WAR - it does not have to be under /axis/* - you could have it be /myservice or similar (I believe, I haven't tried it, just read the article).  Then you in your web.xml could say that /myservice requests should go to a servlet that you wrote yourself or to a JSP page, and then in that servlet or JSP, you could dispatch to the right WSDL file for the client (eg, if you wanted each client to have a different set of <documentation> elements in the WSDL)... 
 
Without knowing what you're trying to do different for each client, that's about the best suggestion I have at the moment...
-----Original Message-----
From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:39 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Turning off ?wsdl feature

Short of writing a filter to intercept the ?wsdl querystring, I am not sure how I trap that request in the web.xml file. Currently, the web.xml has an entry for /axis/* for all services to be handled by the AxisServlet. How would I intercept something like "/axis/*?wsdl"?
-----Original Message-----
From: Mike Burati [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:37 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Turning off ?wsdl feature

 
Use that feature to point it to a resource in your WAR (defined by web.xml) which is a servlet or JSP controller that dispatches to the client-specific actual WSDL based on which client is making the request?
-----Original Message-----
From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:28 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Turning off ?wsdl feature

That works great for only one, but I want to be able to select different WSDL files, not just one. I guess you could conceivably have different service urls for each client, but that gets ugly fast.
-----Original Message-----
From: Kellogg, Richard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:23 PM
To: [EMAIL PROTECTED]
Subject: RE: Turning off ?wsdl feature

Try the following article:
 
-----Original Message-----
From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 4:18 PM
To: '[EMAIL PROTECTED]'
Subject: Turning off ?wsdl feature

Is there a way to limit access to the ?wsdl feature or turn it off completely? I need to be able customize the WSDL file based on the client, so I don't want it readily available to all clients.
 
Thanks,
Ozzie

Reply via email to