Return-Path: 
 <dev-return-6295-apmail-cxf-dev-archive=cxf.apache.org@cxf.apache.org>
Delivered-To: apmail-cxf-dev-archive@www.apache.org
Received: (qmail 19746 invoked from network); 23 Jul 2008 12:22:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Jul 2008 12:22:11 -0000
Received: (qmail 46861 invoked by uid 500); 23 Jul 2008 12:22:08 -0000
Delivered-To: apmail-cxf-dev-archive@cxf.apache.org
Received: (qmail 46815 invoked by uid 500); 23 Jul 2008 12:22:08 -0000
Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cxf.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cxf.apache.org>
List-Post: <mailto:dev@cxf.apache.org>
List-Id: <dev.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list dev@cxf.apache.org
Received: (qmail 46802 invoked by uid 99); 23 Jul 2008 12:22:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jul 2008 05:22:08 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of gnodet@gmail.com designates
 66.249.92.170 as permitted sender)
Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jul 2008 12:21:09 +0000
Received: by ug-out-1314.google.com with SMTP id c2so955002ugf.24
        for <dev@cxf.apache.org>; Wed, 23 Jul 2008 05:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=ReMH9/y/eRwX9FmFWxeNHg9/xTlLhMhFtwN+m9dl0BA=;
        b=JbHi2g8NSlrDeYR9yNox+zjo0EvBKWqfxpkhBQviMOZ8waVnSTQCtJKBfM7wL3lB3U
         nVdwozhRoEluLJh55zXDbGmbtPaxvAMRUhQoF13gnfcNLcWFF6x+4rW8AZdKcSVEwtm8
         cheyODeBkt7M+qcJqhYcWX+wWXwVvhoQ/PsuQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=bBNYFxwbMiPe9NO12vRwjdf/x7DzhKaWO4+IB4rgl9JdWhIPcLC1ig4NzDf3Dew2p2
         i3mxCdpiaWbZPBfXCOqipie05BNA7+hjbwGL42Ma+vEGxItK0ug3pZ6DT10y6zOlKivm
         YvIWUKdMc+eRt7rG4pRyVW95JBqQh69GrNhUI=
Received: by 10.103.220.18 with SMTP id x18mr4552513muq.81.1216815675479;
        Wed, 23 Jul 2008 05:21:15 -0700 (PDT)
Received: by 10.103.244.13 with HTTP; Wed, 23 Jul 2008 05:21:15 -0700 (PDT)
Message-ID: <b23ecedc0807230521w71d08876nf7923c845aaff213@mail.gmail.com>
Date: Wed, 23 Jul 2008 14:21:15 +0200
From: "Guillaume Nodet" <gnodet@gmail.com>
To: dev@cxf.apache.org
Subject: Re: how about we honor style sheet in wsdl
In-Reply-To: <61b5d9410807230505q2ce6e9c9h68aa3b0accfa4bdd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4886D440.1070104@gmail.com>
	 <61b5d9410807230505q2ce6e9c9h68aa3b0accfa4bdd@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

I think the problem is that when served from CXF, the PI is removed
from the original WSDL.

On Wed, Jul 23, 2008 at 2:05 PM, Benson Margulies <bimargulies@gmail.com> wrote:
> I don't follow exactly.
>
> If the URL in the PI were relative, then we could imagine serving it
> up. But as an absolute URL, it's up to the user to configure the
> container to deliver it, no?
>
>
>
> On Wed, Jul 23, 2008 at 2:48 AM, Freeman Fang <freeman.fang@gmail.com> wrote:
>> Hi,
>>
>> For the wsdl like
>> <?xml version="1.0" encoding="UTF-8"?>
>> <?xml-stylesheet type="text/xsl"
>> href="http://api.bioinfo.no/stylesheets/WSDLDocumentation.xslt"?>
>> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
>> ....
>>
>> Is it possible that we publish stylesheet as well when we publish the wsdl,
>> I mean if customer get wsdl from http://serviceaddress?wsdl, they can also
>> see the stylesheet their.
>> Or any reason we shouldn't do it?
>>
>> Thanks
>> Freeman
>>
>>
>>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/