Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: 4.1
-
Component/s: None
-
Labels:None
-
Environment:any
Description
When doing some profiling I noticed that painting thread would sometimes kick off page initialization rather then the pageInitialization thread pool. The first line of the paint method will kick off the page.init(). To avoid this type of intitialization I check to see if a pagePainter object is present, and is always present in the default RI. If present and page initialization hasn't happened we return and wait for the page component to handle the initialization call, page painting will occur later.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Update page class, closing.