Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 21959 invoked from network); 28 Jul 2005 07:40:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jul 2005 07:40:20 -0000 Received: (qmail 67781 invoked by uid 500); 28 Jul 2005 07:40:16 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 67760 invoked by uid 500); 28 Jul 2005 07:40:16 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 67747 invoked by uid 99); 28 Jul 2005 07:40:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 00:40:15 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=HTML_60_70,HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [62.55.240.2] (HELO pmx1.bertelsmann.de) (62.55.240.2) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 00:40:09 -0700 Received: from pmx1.bertelsmann.de (localhost [127.0.0.1]) by localhost.bertelsmann.de (Postfix) with ESMTP id 986BE35356 for ; Thu, 28 Jul 2005 09:40:13 +0200 (CEST) Received: from mmx1.bertelsmann.de (mmxa.wip.bertelsmann.de [145.228.237.30]) by pmx1.bertelsmann.de (Postfix) with ESMTP id 8ED0735224 for ; Thu, 28 Jul 2005 09:40:13 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C59347.4AD5BDD0" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: Feature Request: Use of XML Schema for Interface Restrictions Date: Thu, 28 Jul 2005 09:38:05 +0200 Message-ID: <8D5D39EC0B0AD4119B8000508B6A6767106AC238@debage66.bertelsmann.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Feature Request: Use of XML Schema for Interface Restrictions Thread-Index: AcWTRm/nit+KagZYSa+I2MAx1kMQ+QAAPjGQ From: To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C59347.4AD5BDD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > -----Urspr=FCngliche Nachricht----- > Von: Wegener, Jan, DCO =20 > Gesendet: Donnerstag, 28. Juli 2005 09:31 > An: 'axis-dev@ws.apache.org' > Betreff: Feature Request: Use of XML Schema for Interface Restrictions >=20 > Hello there, >=20 > currently the types generated in the wsdl are just the simple type = mappings like Java:String to XML:String. >=20 > So if you want to restrict the type to certain values you either have = to manually modify the wsdl or write the checks in Java Code. > Wouldn=B4t it be nice to generate some restrictions from the given = interface? > A possible solution could be to use annotations in the interface to = define some basic restrictions: >=20 > @argumentLength(7, 1) to define a maximum length of seven for the = first argument of the method annotated > @argumentPattter("*foobar*", 1) to define a pattern for String = arguments >=20 > The goal is to be able to use the possibilities of XML Schema better = for defing the Web Service Interface with minimal manual modification = since you want to write java code and generate all needed XML out of = your interface. Because writing/modifying WSDL Files by hand is quite = error-prone since the wsdl can become pretty complicated. >=20 > greetings >=20 > Jan Wegener > IT Architecture & Systems > ------------------------------------------------- > arvato direct services > An der Autobahn > 33310 G=FCtersloh > Germany > >=20 ------_=_NextPart_001_01C59347.4AD5BDD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Feature Request: Use of XML Schema for Interface = Restrictions

 -----Urspr=FCngliche = Nachricht-----
Von: =    Wegener, Jan, = DCO 
Gesendet:       = Donnerstag, 28. Juli 2005 = 09:31
An:     'axis-dev@ws.apache.org'
Betreff:       = Feature Request: Use of XML Schema = for Interface Restrictions

Hello = there,

currently the types = generated in the wsdl are just the simple type mappings like Java:String = to XML:String.

So if you want to = restrict the type to certain values you either have to manually modify = the wsdl or write the checks in Java Code.

Wouldn=B4t it be nice = to generate some restrictions from the given interface?
A possible solution = could be to use annotations in the interface to define some basic = restrictions:

@argumentLength(7, 1) = to define a maximum length of seven for the first argument of the method = annotated
@argumentPattter("*foobar*", 1) to define a = pattern for String arguments

The goal is to be = able to use the possibilities of XML Schema better for defing the Web = Service Interface with minimal manual modification since you want to = write java code and generate all needed XML out of your interface. = Because writing/modifying WSDL Files by hand is quite error-prone since = the wsdl can become pretty complicated.

greetings

Jan = Wegener
IT Architecture = & Systems
-------------------------------------------------
arvato direct = services
An der = Autobahn
33310 = G=FCtersloh
Germany
<http://www.arvato.com/>=

------_=_NextPart_001_01C59347.4AD5BDD0--