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 Wicket
(well, maybe if you have just 1 or 2). If you want to be more
powerful, I would rather implement REST stuff with Spring MVC.
Currently I am using Restlets which works very well also. Jersey
sounds fine as well.
I'm aware of the Wicket focus on stateful stuff. But, as you say,
sometimes a few things are stateless - and, yes, I have just a few
resources (three "categories" of objects, each would get its own URL).
So, hmmm, still I don't see a strong motivation to go either way...
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
fabrizio.giud...@tidalwave.it - mobile: +39 348.150.6941
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
