Hi All,I am interested in using wicket as web service framework. We already use it to serve a web and mobile web browser application but now we have a need to open up the API for other types of client and I think it would be great if I can leverage a lot of the wicket work already done like the authentication and form validation.
I see from this blog post that others have thought of this and indeed it shows how to implement a simple web service, however Jonathan's comment below makes a good point as I will also need to handle POST requests http://blog.brunoborges.com.br/2008/11/restful-web-services-with-wicket.html So I am wondering if anyone has taken this further and perhaps we could talk about how to best approach this strategy or perhaps you think I am completely mad to even think about using wicket in this way in which case please do say so.