Bug 980532

Summary: Annotation literals implementing an annotation interface raise a warning in JBDS
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Ron Šmeral <rsmeral>
Component: unspecifiedAssignee: mark yarborough <myarboro>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Karel Piwko <kpiwko>
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.3.0CC: amelicha, maschmid
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-18 15:01:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ron Šmeral 2013-07-02 16:00:30 UTC 
Description of problem:
An annotation literal is a concept defined in Java EE 6, described e.g. in javadoc of http://docs.oracle.com/javaee/6/api/javax/enterprise/util/AnnotationLiteral.html. In this piece of official documentation, an example of usage shows an implementation of an annotation:

public abstract class PayByQualifier 
       extends AnnotationLiteral<PayBy>
       implements PayBy {}

Despite this pattern being defined in the official Java EE documentation, JBDS (Eclipse) warns that annotations should not be used as superinterfaces.

Version-Release number of selected component (if applicable):
WFK 2.3.0.CR1
JBDS 7.0.0.Beta2b

How reproducible:
In a project in JBDS, use the New Annotation Literal wizard to create an Annotation Literal.

Actual results:
A warning is shown, e.g.:
"The annotation type RestRequest should not be used as a superinterface for RestRequestLiteral."

Expected results:
No warning should be displayed as this is an officially endorsed pattern.
Comment 1 Marek Schmidt 2013-07-18 15:01:01 UTC 
Migrated to JIRA as https://issues.jboss.org/browse/WFK2-66