Hi there.
My application, along with the usual HTML pages generated with Wicket,
should also expose some RESTful services. These REST calls should return
documents of various types: images, movies, as well as RDF/XML and N3
and so far.
In an architectural spike I've made, I've used Jersey
Wicket is all about stateful applications (though stateless stuff is
useful and is supported).
REST is all about stateless resources (though you sometimes need
stateful hacks for login/authentication).
Given these premises, I would not implement REST resources with Wicket
(well, maybe if you
Erik van Oosten wrote:
Wicket is all about stateful applications (though stateless stuff is
useful and is supported).
REST is all about stateless resources (though you sometimes need
stateful hacks for login/authentication).
Given these premises, I would not implement REST resources with
