+1 for such solution, this is definitely a limitation that I saw many people facing. Deploying wink as a filter can be a clean and simple solution.
-----Original Message----- From: Davanum Srinivas [mailto:[email protected]] Sent: Wednesday, August 26, 2009 2:26 PM To: [email protected] Subject: Re: Use case - deploy wink as a servlet filter Michael, Example see: http://blog.docuverse.com/2009/08/04/using-jsp-with-jersey-jax-rs-implementation/ Quote from that article: "The primitive servlet-mapping URI pattern scheme, which somehow survived many iterations of the servlet API, impacts JAX-RS hard if servlet-mapping is overly broad. Unfortunately, pretty restful URL calls for servlet-mapping to be "/*" instead of something like "/jersey/*", breaking access to JSP files as well as static resources." thanks, dims On 08/26/2009 07:15 AM, Michael Elman wrote: > I'm not sure I understand what is the use case to deploy Wink as a > servlet filter. > Technically IMO it's not difficult to provide such functionality. > > On Wed, Aug 26, 2009 at 5:18 AM, Davanum Srinivas<[email protected]> wrote: >> Team, >> >> Do we support deploying wink as a servlet filter? I was looking at htmleasy >> [1] and found this use case [2] >> >> thanks, >> dims >> >> [1] http://code.google.com/p/htmleasy/ >> [2] >> http://code.google.com/p/htmleasy/source/browse/trunk/src/main/java/com/googlecode/htmleasy/ResteasyFilter.java >>
