Was just talking with my work friend Craig about REST interfaces when it occurred to us that you could create a really nice object-oriented REST interface where Wicket components implement RESTy methods, like onCreate, onDelete, onUpdate and onGet.  Ideally, it would be a generic design with pluggable representations and nice listener methods on the server (potentially abstracting parameter encoding via Wicket URL encoding strategies in a useful way). Drawing from the ideas from an enterprise logging framework I’m hopefully going to open source soon, restful objects might implement an interface like Restable, which would allow a given object to produce a representation of itself based on the parameters of a particular REST request. On the client side, abstracted parameters would be encoded by the reverse side of a Wicket encoding strategy and the whole thing would round trip seamlessly and with nothing but objects involved.