Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCC2F399E for ; Sun, 8 May 2011 05:06:33 +0000 (UTC) Received: (qmail 28326 invoked by uid 500); 8 May 2011 05:06:33 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 27860 invoked by uid 500); 8 May 2011 05:06:32 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 27852 invoked by uid 99); 8 May 2011 05:06:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 May 2011 05:06:31 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_FONT_FACE_BAD,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of peeyush@metadesignsolutions.com designates 69.175.33.194 as permitted sender) Received: from [69.175.33.194] (HELO cl60.justhost.com) (69.175.33.194) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 May 2011 05:06:26 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=metadesignsolutions.com; h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=GwBRglug3qkX7sVI5dgCLFQEz10gULQRNapCU3IaWztQcZmQWwKpz/vUpGCMw3JNcRhQGnRqRZ9fawQrl1o8izoQA8G55wIjxfEUjyMaNLAZbniX72gakA1FfBiBRveQ; Received: from [182.64.231.52] (helo=[192.168.1.2]) by cl60.justhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1QIwBx-0003JQ-Vl for java-dev@axis.apache.org; Sun, 08 May 2011 00:06:08 -0500 From: Peeyush Tuli Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-3-106439014 Subject: Re: block ?wsdl url Date: Sun, 8 May 2011 10:35:53 +0530 In-Reply-To: To: java-dev@axis.apache.org References: Message-Id: <25904FE6-9C00-400D-9D0B-54BB03BA403C@metadesignsolutions.com> X-Mailer: Apple Mail (2.1084) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cl60.justhost.com X-AntiAbuse: Original Domain - axis.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - metadesignsolutions.com X-Source: X-Source-Args: X-Source-Dir: --Apple-Mail-3-106439014 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks for the reply, Is there a scheduled date for the next release of axis2 as of now?=20 Thanks, Peeyush On May 8, 2011, at 12:11 AM, Afkham Azeez wrote: > In the current Axis2 trunk, you can add the following parameter to the = services.xml file to disable ?wsdl >=20 > false >=20 > This will be available with the next Axis2 release. >=20 >=20 > On Sat, May 7, 2011 at 1:20 PM, Peeyush Tuli = wrote: > Hi, >=20 > 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 -=20 >=20 > http://wso2.org/library/112 >=20 > 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?=20 > Apache rules dont seem to work in mod_jk so it has to done at the = tomcat level only. >=20 > Thanks, > Peeyush >=20 >=20 >=20 > --=20 > Afkham Azeez > Director of Architecture; WSO2, Inc.; http://wso2.com,=20 > Member; Apache Software Foundation; http://www.apache.org/ >=20 > email: azeez@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez >=20 > Lean . Enterprise . Middleware >=20 >=20 --Apple-Mail-3-106439014 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
In the current Axis2 trunk, you can add the following = parameter to the services.xml file to disable = ?wsdl

<parameter = name=3D"

This will be available with the = next Axis2 release.


On Sat, May 7, 2011 at 1:20 PM, Peeyush Tuli <peeyush@metadesignsolution= s.com> 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 - 


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 = ArchitectureWSO2, = Inc.; http://wso2.com
Member; Apache Software = Foundation; http://www.apache.org/

email: azeez@wso2.com cell: +94 77 3320919
blog: 
http://blog.afkham.org
twitter: 
http://twitter.com/afkham_azeez=
linked-in: 
http://lk.linkedin.com/in/afkhamazeez
=

Lean . = Enterprise . Middleware



= --Apple-Mail-3-106439014--