In the current Axis2 trunk, you can add the following parameter to the
services.xml file to disable ?wsdl

<parameter name="exposeServiceMetadata">false</parameter>

This will be available with the next Axis2 release.


On Sat, May 7, 2011 at 1:20 PM, Peeyush Tuli <
[email protected]> wrote:

> Hi,
>
> We have an axis2 deployment which is exposed over the web. The deployment
> is on a tomcat 6.0 with Apache 2.2.3 as the proxy using mod_jk. The customer
> has imposed a restriction that wsdl should not be available over a url like
> it is using http://services/myservice?wsdl . In the wiki, i found this
> link -
>
> http://wso2.org/library/112
>
> <http://wso2.org/library/112>I placed blank wsdl document inside META-INF.
> Using this the ?wsdl url also returns blank but the services stop working
> since the axis parser seems to parse the incoming packets based on the
> custom wsdl only. Isn't there any other simpler way to achieve this?
> Apache rules dont seem to work in mod_jk so it has to done at the tomcat
> level only.
>
> Thanks,
> Peeyush
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*
*
*email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*

Reply via email to