JDK-6669869 : Beans.isDesignTime() and other queries should be per-AppContext
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-29
  • Updated: 2013-08-19
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b55Fixed
Related Reports
Relates :  
JDK-7186718 - Beans.isdesigntime return false in jdk 7u2 even beans.setdesigntime(true) called
Relates :  
JDK-8023310 - Thread contention in the method Beans.IsDesignTime()
Description
Beans.isDesignTime() and other queries should be per-AppContext. We have run into situations in NetBeans where people want to use JOGL both in the Matisse GUI builder and as a plugin in NetBeans. In order to operate within Matisse JOGL requires that Beans.isDesignTime() returns true, but if that is set globally for the entire NetBeans application then plugins which use JOGL will never display any content, since JOGL disables its OpenGL work based on the query of this property.

This and other properties on the Beans class should be per-AppContext, if it is acceptable to add a tie between the Beans class and the sun.awt package. If not then some other way of scoping the query should be invented.
One bug report describing the problem can be seen at
http://www.netbeans.org/issues/show_bug.cgi?id=127935
Comments
EVALUATION The static properties designTime and guiAvailable should use AppContext.
29-01-2009