> > Even the Atom example ultimately describes a single-
> > endpoint service.
>
> The Atom example shows how to describe a particular instance of an
> Atom service using the technique noted above to define the components
> of the Atom Publishing Protocol separately from a concrete
> instantiation of the protocol.
Right, but in the end it describes one and only one concrete
instantiation of the protocol. That means every single Atom service
in the entire world-wide web (a pretty big place, if you will) needs
a separate WADL description, even if they are all identical except
for the host and port.
> > Would it make sense to allow the base URI to have parameters?
>
> It might, do you have a particular use-case in mind ?
You betcha:
<resources base="
http://{servicehost}:{serviceport}/">
<param name="servicehost" style="template" required="true" />
<param name="serviceport" style="template" type="xsd:unsignedShort"
default="80" />
...
</resources>
Suppose I want to use wadl2java to generate a client stub for a
service, and that service isn't unique, but might be installed
anywhere on the Internet. Then it seems I really need something like
this, or I'll have to generated a new stub for every installation of
the service.
joe