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.
Java module version 1.7 This feature is being filed as a response to a posting on NetBeans mailing lists - http://www.netbeans.org/servlets/ReadMsg?msgId=166043&listName=nbdev My module recognizes certain .xml files as its own. These xml files could have corresponding java/class files too. The module has to identify the java/class files as secondary entries, because it isn't mandatory that they exist for every xml file that is recognized by the module. I would like to be able to recognize java files as secondary, yet leverage the java module code - so that the source editor, source node, bean patterns etc show up as they do for a regular java file but as a part of my XML node. Looking at the code for JavaDataObject, it appears as if the java module is quite tightly tied to a java source file being the primary file. The workaround is to use a pointer to the JavaDataObject from my xmlDataObject. But this does not solve the problem because actions like Source Control checkouts that are performed should check out *both* files. The only way both files are treated as a single unit is by using a multidataobject that uses the xml as primary, and the java as secondary. This capability is quite important to the application that we are developing. Thanks.
Cleaning up before 4.0 planning
Target milestone was changed from not determined to TBD
does this issue apply to NB5 anymore?
probably out-dated by now. closed as won't fix.