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.

Bug 18343 - Use Java source file as secondary entry
Summary: Use Java source file as secondary entry
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on: 12238 12331
Blocks:
  Show dependency tree
 
Reported: 2001-12-04 18:12 UTC by Kale
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kale 2001-12-04 18:12:45 UTC
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.
Comment 1 Svata Dedic 2002-05-21 17:51:05 UTC
Cleaning up before 4.0 planning
Comment 2 Marek Grummich 2002-07-19 16:06:20 UTC
Target milestone was changed from not determined to TBD
Comment 3 _ alexlamsl 2005-12-01 01:03:02 UTC
does this issue apply to NB5 anymore?
Comment 4 _ alexlamsl 2005-12-01 15:39:29 UTC
probably out-dated by now.

closed as won't fix.