Closed glassfishrobot closed 14 years ago
@glassfishrobot Commented ludo said: for Rogerk
@glassfishrobot Commented ludo said: For other spec leads to verify their APIs, they can look at http://javadoc.glassfish.org/javaee6/apidoc/
to see if everything is correct... This should be a mandatory step before we ship, to have the green light from all the spec leads there.
@glassfishrobot Commented rogerk said: The Weld osgi bundle jar contains:
javax.inject.Named (330) javax.enterprise.inject.StereoType
It does not container NonBinding
Agreed that Named, Stereotype and NonBinding must be removed from javax.annotations.jar
@glassfishrobot Commented ludo said: but there is a javadoc for it: ( see my link)
javax.enterprise.inject Annotation Type Nonbinding
@Retention(value=RUNTIME) @Target(value=METHOD) public @interface Nonbinding Specifies that a member of a binding type or interceptor binding type is to be ignored for the purposes of resolution.
Author: Gavin King
Maybe obsolete as well?
@glassfishrobot Commented rogerk said: Named.java, Stereotype.java and NonBinding.java have ben svn deleted from v3/javaee-api/javax.annotation/src/main/java/javax/annotation. They will not be included in javax.annotation jar when building v3.
@glassfishrobot Commented Was assigned to rogerk
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-11016
@glassfishrobot Commented Reported by ludo
@glassfishrobot Commented Marked as fixed on Thursday, November 12th 2009, 1:17:03 pm
I see in javax.annotations.jar 3 annotations that should not be there: Named StereoType NonBinding
They should be in javax.entreprise.inject * (and they are as well, but need to verify)
I guess our TCK does not have APIs validation for extra classes that are not part of the Java EE 6 spec?
P1, cannot ship with these.
(ps: I discovered that by using Eclipse and NetBeans editor code completion and I was annoyed of seeing 2 classes for Named)
Environment
Operating System: All Platform: All
Affected Versions
[V3]