RE: Updated WADL Spec

From: Ole Matzura <>
Date: Wed, 4 Feb 2009 16:10:36 +0100

Hi Marc,

Thank you! When do you expect these changes to become "official" and part of
a release of some sort (maybe they already are)? I am asking since we have
rather extensive WADL support in soapUI for the "previous version" and are
asking ourselves if we should hurry to implement this or wait until it is

To what extent has the previous version been adopted by tools and
developers? Should we maintain backwards compatibility for both importing
and generating WADL files? Or just importing?


 Ole Lensmar
 tel: +46 (0)703 555 000
 fax: +46 (0)8 790 61 19

-----Original Message-----
From: Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
Sent: Monday, February 02, 2009 23:04
Subject: Updated WADL Spec

I've uploaded a draft updated specification and the schemas to:

Changes since the November 2006 Publication:

- The namespace was changed to
- Resolved issue 13. The status attribute was moved from the
representation element to the
response element. The cardinality of the response element was changed
from 0-1 to 0-many.
The fault element was removed.
- Resolved issue 17. Allow parameters at top level and parameter
references to prevent repetition when
a parameter is used in multiple places.
- Resolved issue 18. A resource type element may now contain resource
child elements.
- Resolved issue 20. Allow multiple resources elements within an
- Updated the Atompub example to RFC syntax.

Unfortunately the changes required by issue 13 were not backwards
compatible so I had to change the namespace and existing WADL docs
will require minor edits as a result.

I haven't updated the wadl2java code to support these changes yet,
I'll be working on that next. In the meantime I'd be grateful if one
or more of you could sanity check the updated spec and schemas.


Marc Hadley <marc.hadley at>
CTO Office, Sun Microsystems.
To unsubscribe, e-mail:
For additional commands, e-mail: