very nice work from Brett, but then I started to evaluate the trend
between formalism and service payload:
so, using curl:
curl -H "Accept:application/json" -X GET
"
http://fgaucho.dyndns.org:8080/hateoas4legacy/rs/countries/AU"
{"links":{"link":[{"@rel":"","@type":"locator","@href":"
http://fgaucho.dyndns.org:8080/hateoas4legacy/rs/cities/Brisbane"},{"@rel":"","@type":"locator","@href":"
http://fgaucho.dyndns.org:8080/hateoas4legacy/rs/cities/Sydney"},{"@rel":"","@type":"locator","@href":"
http://fgaucho.dyndns.org:8080/hateoas4legacy/rs/cities/Melbourne"},{"@rel":"","@type":"locator","@href":"
http://fgaucho.dyndns.org:8080/hateoas4legacy/rs/countries/AU"}]},"cities":{"city":[{"links":null,"name":"Brisbane"},{"links":null,"name":"Sydney"},{"links":null,"name":"Melbourne"}]},"isoCode":"AU","name":"Australia"}
seems too much data ... adherent to XML/XLink specification but
perhaps too much verbose for JSON formats..
very nice to know it works.. and that all XML semantic can be
implemented in Jersey, but I will leave this specific topic open for a
further need.. for now I will just drop the URL inside an element..