This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | @WarmUp | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | Module System | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | issues, thurka |
Priority: | P3 | Keywords: | API, PERFORMANCE |
Version: | 7.2 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 97628 | ||
Bug Blocks: | 200636 |
Description
Jesse Glick
2012-04-04 14:34:42 UTC
I'd like to avoid creation of @WarmUp annotation at all. The analysis done by Tomáš Hůrka shows that many usages of that annotation are completely wrong (mobility, JSP, etc.). We don't need to pre-heat JSP unless we know somebody is going to open a JSP editor. In such case, the pre-heating can happen in the JspEditorKit.call() method (if it implements java.util.concurrent.Callable). We don't want to do anything with mobility unless mobility project is opened or created. Again, @WarmUp is not the right place to do such kind of warm up. According to Tomáš, some of the warmup tasks need to be executed - those would be better with @OnShowing or @OnStart annotation anyway. If there is anything left (and I would guess it is less then five cases), I'd rather stick with less visible @ServicerProvider(path) registration then invent special API for such questionable concept as @WarmUp. Performance guys may of course, have a different point of view. Makes sense. Is there an issue open to actually go through the 13 existing tasks and classify them accordingly? Tomáš was driving the process of classifying and cleaning up warm up tasks... |