On Feb 4, 2009, at 10:10 AM, Ole Matzura wrote:
>
> 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
> finalized.
>
If there's no substantive feedback on the current draft within the
next couple of weeks then I'll push it out as a "official" release.
Until then please consider the latest spec as a draft and liable to
change. It was a shame to have to break backwards compatibility due to
issue 13 but I think the result is significantly more logical and
expressive I think.
> To what extent has the previous version been adopted by tools and
> developers?
I haven't been tracking adoption all that closely but I'm aware of
support in one form or another in the following: NetBeans, Eclipse,
Zembly, Kapow, WaveRider and soapUI.
> Should we maintain backwards compatibility for both importing
> and generating WADL files? Or just importing?
>
That's a tough question, I suspect it will take a while for all the
tools to support the new version so it might be best to support import
and generation of both versions for a while. It really depends on how
your users are using WADL and what other tools they are using.
Regards,
Marc.
>
> -----Original Message-----
> From: Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
> Sent: Monday, February 02, 2009 23:04
> To: users_at_wadl.dev.java.net; dev_at_wadl.dev.java.net
> Subject: Updated WADL Spec
>
> I've uploaded a draft updated specification and the schemas to:
>
> http://wadl.dev.java.net/wadl20090202.pdf
> http://wadl.dev.java.net/wadl20090202.rnc
> http://wadl.dev.java.net/wadl20090202.xsd
>
> Changes since the November 2006 Publication:
>
> - The namespace was changed to http://wadl.dev.java.net/2009/02.
> - 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
> application.
> - 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.
>
> Thanks,
> Marc.
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_wadl.dev.java.net
> For additional commands, e-mail: users-help_at_wadl.dev.java.net
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_wadl.dev.java.net
> For additional commands, e-mail: users-help_at_wadl.dev.java.net
>
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.