Just found out about @Singleton and @PerRequest. In light of
transparency/familiarity, is there a good reason for these not to be
named @Application and @Request respectfully? It seems like Application
> Session > Request > ThreadLocal, is a well established naming
standard regarding scopes in web frameworks.
Or even better, @Scope(ResourceScope.APPLICATION) and
@Scope(ResourceScope.REQUEST) as that would tie them together a little.
Semantically they are mutually exclusive even though Jersey currently
allows both to be used on the same resource (which one takes precedence
and why?).
/Casper