-
Bug
-
Resolution: Fixed
-
P4
-
9
-
None
-
b78
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8135838 | emb-9 | Alexander Stepanov | P4 | Resolved | Fixed | team |
The following unit tests were added while fixing JDK-4058433:
jdk/test/java/beans/Introspector/4058433/TestJavaBean.java
jdk/test/java/beans/Introspector/4058433/TestBeanProperty.java
jdk/test/java/beans/Introspector/4058433/TestSwingContainer.java
The following test cases should be added for the annotations:
JavaBean, SwingContainer: check if "this annotation is not used if the annotated class has a corresponding user-defined BeanInfo class" (according to the spec.).
jdk/test/java/beans/Introspector/4058433/TestJavaBean.java
jdk/test/java/beans/Introspector/4058433/TestBeanProperty.java
jdk/test/java/beans/Introspector/4058433/TestSwingContainer.java
The following test cases should be added for the annotations:
JavaBean, SwingContainer: check if "this annotation is not used if the annotated class has a corresponding user-defined BeanInfo class" (according to the spec.).
- backported by
-
JDK-8135838 [TEST] bean annotations: add a test checking if a separate user-defined BeanInfo class is top-priority as compared with the annotations.
- Resolved
- relates to
-
JDK-8131342 new @BeanProperty annotation: could we specify more than one per bean?
- Closed
-
JDK-4058433 RFE: tool for creating BeanInfo template
- Resolved
-
JDK-8132138 Create some tests according to SQE Test Plan for BeanInfo Annotations
- Resolved