Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 66948 invoked from network); 30 Jul 2007 19:25:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jul 2007 19:25:34 -0000 Received: (qmail 74922 invoked by uid 500); 30 Jul 2007 19:25:32 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 74853 invoked by uid 500); 30 Jul 2007 19:25:31 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 74806 invoked by uid 99); 30 Jul 2007 19:25:31 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 12:25:31 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of bim2007@basistech.com does not designate 199.88.205.99 as permitted sender) Received: from [199.88.205.99] (HELO mail.basistech.com) (199.88.205.99) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 19:25:25 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7D2DF.5357B57E" Subject: wsdl2js, namespace prefixes Date: Mon, 30 Jul 2007 15:25:02 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: wsdl2js, namespace prefixes Thread-Index: AcfS31OqJpsUzQ2oRNinHNdYs1cweQ== From: "Benson Margulies" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C7D2DF.5357B57E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable When we built wsdl2js, we were working with a soap toolkit that allowed us to control the namespace prefixes used in the WSDL (and the actual wire protocol). This had a happy side-effect: we could assume 'presentable' prefixes, and use them as parts of JavaScript identifiers. =20 As far as I've ever figured out, XFire (and presumably CXF) don't cater to people with feelings about prefixes, so we've got things in tns: and things in ns0: and ns1: etc. =20 For JavaScript generation, I hate to force the user to supply some sort of additional file to hand out prefixes. Is there some JAX-WS annotation that would allow CXF to allow someone or something to spec out the namespaces? Aegis has a mechanism that, sadly, doesn't quite work. I spent some time on it in XFire and couldn't quite adapt the code to do it. =20 ------_=_NextPart_001_01C7D2DF.5357B57E--