Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 77207 invoked from network); 8 Dec 2009 23:25:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Dec 2009 23:25:26 -0000 Received: (qmail 71724 invoked by uid 500); 8 Dec 2009 23:25:24 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 71672 invoked by uid 500); 8 Dec 2009 23:25:23 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 71663 invoked by uid 99); 8 Dec 2009 23:25:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 23:25:23 +0000 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=HTML_MESSAGE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.220.227] (HELO mail-fx0-f227.google.com) (209.85.220.227) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 23:25:15 +0000 Received: by fxm27 with SMTP id 27so6260543fxm.23 for ; Tue, 08 Dec 2009 15:24:55 -0800 (PST) From: Michael Rohleder MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acp4XacdA8C7cc85S7G5DEYMrI9Fnw== Date: Wed, 9 Dec 2009 00:24:56 +0100 Received: by 10.239.163.225 with SMTP id q33mr1028117hbd.137.1260314694802; Tue, 08 Dec 2009 15:24:54 -0800 (PST) Message-ID: <2558344872737543330@unknownmsgid> Subject: Providing rpc/encoded jax-ws webservice To: axis-user@ws.apache.org Content-Type: multipart/alternative; boundary=00163645705eb05f48047a3fe1c8 X-Virus-Checked: Checked by ClamAV on apache.org --00163645705eb05f48047a3fe1c8 Content-Type: text/plain; charset=ISO-8859-1 Hi, does anybody have a solution for providing a rpc-encoded jax-ws webservice for backward compatibility and for giving clients time to migrate to a new document-literal webservice? I think xml transformation (rpc-encoded <-> document-literal) could be possible, like this: http://www.cafebabe.me/2007/03/migrating-smoothly-from-rpcencoded-to.html It detects the incoming rpc/encoded requests and transform them to the new structure. Unfortunately this is not a generic transformation solution, the xsl is implemented for a specific service...perhaps anyone have a idea for generic way? Are there other solutions (generators, handlers, ...)? Thanks. Michael. --00163645705eb05f48047a3fe1c8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi,
does anybody have a solution for providing a rpc-encoded jax-ws webservice = for backward compatibility and for giving clients time to migrate to a new document-literal webservice?

I think xml transformation (rpc-encoded <-> document-literal) could b= e possible, like this: http://www.cafe= babe.me/2007/03/migrating-smoothly-from-rpcencoded-to.html
It detects the incoming rpc/encoded requests and transform them to the new structure. Unfortunately this is not a generic transformation solution, the= xsl is implemented for a specific service...perhaps anyone have a idea for gene= ric way?

Are there other solutions (generators, handlers, ...)?

Thanks.

=A0

Michael.

--00163645705eb05f48047a3fe1c8--