When I filed the original request for JAX-RS specific filters (in contrast
to proprietary Jersey filters or to environment dependent Servlet filters) I
had in mind mostly the filters we needed to implement Microsoft-compatible
WebDAV dialects. All of them must be pre-matching, as they modify URLs and
method names. But certainly there may be other use cases where post-matching
makes sense. So my vote goes for pre-match as default, which induces a need
for an explicit post-match annotation.
> -----Original Message-----
> From: Marek Potociar [mailto:marek.potociar_at_oracle.com]
> Sent: Freitag, 15. Juni 2012 13:03
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: [jax-rs-spec users] @PostMatch vs.
> @PreMatch
>
> Contrary to RestEasy, Jersey does often use pre-match filters. But I'm
> fine discussing which annotation would be more convenient.
>
> Marek
>
> On Jun 11, 2012, at 10:47 PM, Bill Burke wrote:
>
> > I don't know about Jersey or CXF, but I do not have any prematch
> "filters" (well, the resteasy equivalent to filter). Was wondering if
> maybe prematch is an edge case, and the more often used case would be
> postmatch.
> >
> > Bill
> >
> > --
> > Bill Burke
> > JBoss, a division of Red Hat
> > http://bill.burkecentral.com
> >