Makes ApplicationPath a bean defining annotation

[spericas]

Description

Makes @ApplicationPath a bean defining annotation. New functional test that shows support for this new feature.

See #8502

Documentation

Needs to be updated

[ljnelson]

(…which normally means it is therefore in @Dependent scope, since you've made it a bean. Is that OK? Maybe @ApplicationPath should be a CDI stereotype, which can explicitly include scopes?)

[spericas]

Yes, in the same way resources are in @Dependent scope by default. Jersey should still create an instance "per application".

[ljnelson]

Personally I'm mildly -1 for these kinds of changes, as making @Path and @ApplicationPath and so on bean-defining annotations is a little bit mysterious. I think everything we do via this mechanism could be done using stereotypes instead, which are inherently bean-defining and can be tested, inspected, etc. at runtime, but I'm not honestly sure.

[spericas]

Personally I'm mildly -1 for these kinds of changes, as making @Path and @ApplicationPath and so on bean-defining annotations is a little bit mysterious. I think everything we do via this mechanism could be done using stereotypes instead, which are inherently bean-defining and can be tested, inspected, etc. at runtime, but I'm not honestly sure.

I understand, but as @romain-grecourt pointed out, it is inconsistent the way it is now between @Path and @ApplicationPath, and that's confusing for developers. Going back on @Path would be backward incompatible.