Then I will add the following before the previous paragraph:
-----
The following are the annotations in javax.servlet. All of these have
corresponding deployment descriptor metadata covered by the Web xsd.
from javax.servlet.annotation:
HttpConstraint
HttpMethodConstraint
MultipartConfig
ServletSecurity
WebFilter
WebInitParam
WebListener
WebServlet
The following annotations from related packages are also covered
by the Web descriptor.
from javax.annotation.*
PostConstruct
PreDestroy
Resource
Resources
DeclareRoles
RunAs
DataSourceDefinition
DataSourceDefinitions
from javax.jms:
JMSConnectionFactory
JMSConnectionFactoryDefinition
JMSConnectionFactoryDefinitions
JMSDestinationDefinition
JMSDestinationDefinitions
from javax.mail:
MailSessionDefinition
MailSessionDefinitions
from javax.interceptor:
AroundConstruct
AroundInvoke
AroundTimeout
ExcludeClassInterceptors
ExcludeDefaultInterceptors
Interceptors
from javax.jws:
WebService
WebMethod
from javax.persistence:
PersistenceContext
PersistenceContexts
PersistenceUnit
PersistenceUnits
from javax.resource:
AdministeredObjectDefinition
AdministeredObjectDefinitions
ConnectionFactoryDefinition
ConnectionFactoryDefinitions
from javax.xml.ws:
WebServiceRef
WebServiceRefs
-----
Shing Wai Chan
On 9/25/15, 1:37 PM, Mark Thomas wrote:
> On 25/09/2015 19:04, Shing Wai Chan wrote:
>> Since there are some confusion of precise meaning of metadata-complete =
>> true
>> with regard to annotation scanning, we would like to made clearer in our
>> spec what
>> it means.
>>
>> I propose to add the following clarification in Section 8.1 of Servlet
>> spec:
>> -----
>> Annotations that do not have equivalents in the deployment XSD include
>> javax.annotation.annotation.HandlesTypes and all of the CDI-related
>> annotations,
>> and must be processed during annotation scanning.
>> -----
>>
>> Please let me know if you see any problems.
> Might it be clearer if we explicitly listed all the annotations that are
> to be ignored if metadata-complete = true ?
>
> Mark
>