On Mon, Jun 24, 2013 at 5:39 PM, Andrea Del Bene <[email protected]>wrote:
> Nice :) ...but I need some more clarifications about your idea. I mean, > JAX-RS is basically a set of annotations to build REST services and > basically what I'd like to have is a Wicket resource that supports them. > But you talk also about a possible integration (via WicketSessionFilter) > with other frameworks that already support this kind of annotations. > These are two distinct topics. Have I understood right? > Right. The original idea was to create an IRequestHandler that knows how to read such annotations and execute the proper method of IResource passing the correct arguments. But this will take time to implement. So I think it will be easier to just use your favorite rest library and wrap it in WicketSessionFilter to provide access to Application and Session thread locals. > Hi Andrea, >> >> This was my "crazy idea" at Ideas for >> Wicket+7.0<https://cwiki.**apache.org/confluence/display/** >> WICKET/Ideas+for+Wicket+7.0#**IdeasforWicket7.0-** >> ImplementJAXRSontopofWicketIRe**source<https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+7.0#IdeasforWicket7.0-ImplementJAXRSontopofWicketIResource> >> > >> >> . >> It should be easy to make an integration with Resteasy, Jersey, Spring >> MVC, >> ... and process any Wicket IResource for such annotations. But the work to >> do this will be definitely more than just use the respective technology >> and >> wrap its Servlet/Filter within WicketSessionFilter. This way you will have >> all that the technology gives you + the Wicket Application and Session >> thread locals. The only thing that will miss is the RequestCycle. >> >> >> On Sat, Jun 22, 2013 at 8:30 PM, Andrea Del Bene <[email protected] >> >wrote: >> >> Hi, >>> >>> In a project I'm following at work we use Spring MCV and its annotations >>> to build a REST service mapping the methods of a controller to a specific >>> path: >>> >>> @Controller >>> @RequestMapping("/users/"){ >>> public MyController { >>> >>> @RequestMapping("/users/{****userid}", method=RequestMethod.GET) >>> >>> public String getUser(@PathVariable String userId) { >>> // implementation omitted... >>> }... >>> >>> .... >>> >>> Is there something similar in WicketStuff or in any other project that >>> allows us to map the methods of a custom resource in a similar way? >>> >>> ------------------------------****----------------------------** >>> --**--------- >>> To unsubscribe, e-mail: >>> users-unsubscribe@wicket.**apa**che.org<http://apache.org> >>> <users-unsubscribe@**wicket.apache.org<[email protected]> >>> > >>> >>> For additional commands, e-mail: [email protected] >>> >>> >>> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
