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.
When creating action for my loader it took some time before I realized I should use my data object class into the cookie class field. There are DataObject.class, EditorCookie.class, etc., prepopulated. This does not seem to be what most users will want to do. Who wants to add an Action to every node which has OpenCookie? Maybe we should look into the manifest of the module and list at least all the defined DataLoaders.
Perhaps true. Depends on what you are making the action for, I guess. What I would suggest: use javamodel etc. to scan the current project for any class which (directly or indirectly) implements Node.Cookie, and add all such entries to the list.
I originally wanted to propose something similiar, but. First, we do not want to propagate the Node.Cookie that much I think. Second, as we use node's lookup there is no such constraint as having the class implementing Node.Cookie. (I might be wrong here)
CookieAction uses Node.getCookie and requires Node.Cookie implementations.
Not for 5.0
I'm not working on APISupport anymore. Reassigning to owner of the component, so the issue is not 'forgotten' forever.
No clear list of things which you might want your action to be sensitive to.