One of the features added to WADL in the latest revision of the specification was the ability to embed parameters in resource path definitions. E.g., the following describes a set of resources identified by a parameterized URI:
In a previous entry I described some enhancements that were under consideration for an updated version of the WADL specification.
In this entry I describe some of the language enhancements that will be in the next version of the WADL specification.
In previous entries I've shown how to use the JAX-WS APIs to publish and use RESTful Web services. Up till now I've focussed mainly on XML/HTTP since this is what most services use but JAX-WS can also handle other kinds of data.
The Web Application Description Language (WADL) specification has now been published as a Sun Labs Technical Report (TR-153).
In a previous blog entry I described how to use the dynamic client functionality of JAX-WS in combination with JAXP XPath capabilities to query a service providing data using XML/HTTP. In this entry I'd like to focus on how to use JAXB instead of XPath to get strongly typed access to the same data.
The first thing to do is work out the IP address of the Airport base station to which you've hooked up the printer. The Airport Admin utility on a Mac can help out here if you have multiple base stations but if you have only one then its likely to the same IP address that is your default gateway. To find the default gateway type (the # represents the shell prompt, don't type it):