After I wrote my original follow-up to Thomas' message, I thought of having different services - one for methods that require authentication, and one for those that don't. Then I can map my ServletFilter to the URL for the service that requires authentication, and not map it to those that don't.
That seems easier to me than the annotation route. Anyone have any reasons to think otherwise? Ryan On Jun 5, 8:22 am, Jens <jens.nehlme...@gmail.com> wrote: > > You can create your own custom annotation (for example : LoggedIn). Apply > > this on all methods you want to authenticate the user/ session to be > > validated. > > Better do it the opposite way if you only have few methods that are allowed > for unauthenticated users (I think thats more typically), e.g. create a > @AllowUnauthenticated annotation and if its absent assume the user must be > logged in. That way you have few "opt-out" methods instead of many "opt-in" > methods. > > -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
