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.
There is a calling API for adding node factories to ClassDataObject/JavaDataObject that is used e.g. by Beans module and JavaDoc module. If would be better to use declarative way of specifying node factories, e.g. using module layers and Lookup. It would save Beans module some instalation work (its ModuleInstall can then go away totaly) and spase some classes at startup (7 for clazz module, maybe some(up to 20 when some other criterion will be met) for java module, 6 for beans module)
BTW: When connected with the change I've just made to not resolve FormDataObject from i18n.form.I18nFormCrossModule, it can really spare ~21 classes of Java module at startup
Reassinging to netbeans.org mailing address.
Also can cause early loading of SourceOptions, increasing priority.
Adding people, who I know to use node factories, on the CC: list
Created attachment 2291 [details] Proposed patch for the javadoc module
Fixed in the dev trunk. Factory chains are lazily initialized upon the first java/clazz node creation. Instances of factories are taken from the module layers. Note, that layer-based factories always get precedence over manually added ones. Patch for javadoc module is provided. Clazz module listens on "NodeFactories/clazz" rather than NodeFactories/java to allow attaching factory specifically to one of the modules.
Verified.