-
Bug
-
Resolution: Not an Issue
-
P2
-
None
-
7u2
-
generic
-
generic
SHORT SUMMARY:
beans.isdesigntime returns false in jdk 7u2 even if beans.setdesigntime(true)
is called
INDICATORS:
When JDeveloper is started, it would call Bean.setDesignTime(true). In the
older jdk7 (e.g. 1.7.0-b147), calling Beans.isDesignTime() later in other UI
thread would return true. However, when using jdk7u2, isDesignTime() does
not return true if it is called from a different ThreadGroup. This is a
change in behavior and causes regression in our product.
COUNTER INDICATORS:
no delay
TRIGGERS:
1.7.0.2
KNOWN WORKAROUND:
na
PRESENT SINCE:
1.7.0.2
HOW TO VERIFY:
test case provided
NOTES FOR SE:
None
REGRESSION:
yes
beans.isdesigntime returns false in jdk 7u2 even if beans.setdesigntime(true)
is called
INDICATORS:
When JDeveloper is started, it would call Bean.setDesignTime(true). In the
older jdk7 (e.g. 1.7.0-b147), calling Beans.isDesignTime() later in other UI
thread would return true. However, when using jdk7u2, isDesignTime() does
not return true if it is called from a different ThreadGroup. This is a
change in behavior and causes regression in our product.
COUNTER INDICATORS:
no delay
TRIGGERS:
1.7.0.2
KNOWN WORKAROUND:
na
PRESENT SINCE:
1.7.0.2
HOW TO VERIFY:
test case provided
NOTES FOR SE:
None
REGRESSION:
yes
- relates to
-
JDK-7064279 Introspector.getBeanInfo() should release some resources in timely manner
-
- Closed
-
-
JDK-6669869 Beans.isDesignTime() and other queries should be per-AppContext
-
- Closed
-