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.
[dev jan 16] With the XML module installed, node delegates for XML files produced via XMLDataObject.Processor or .Environment are not honored, and the plain XML node is used instead. This breaks apisupport's layer editing feature and contradicts the API. Please either do what org.openide.loaders.XMLDataObject does, and use the supplied node as the object's node delegate, or include that node as a subnode, etc. Of course for the future this style should be deprecated in favor of Looks, but that is not yet ready, and older modules using the existing API ought to be able to work anyway.
XML module is in similar situation as your modules. Imagine that XML module also registered an Environment. Who wins? No rules are defined. Ok, there is a workaround: set netbeans.xml.uselooks=true property (it is sampled at startup) and then set "Basic" look at XML node. It should work (sometimes "Basic" look must set twice :-(). If it works for you then reconsider the P2, please.
I know the API is not great. Nevertheless no other module *does* register anything against this DTD, so there is no reason why the API has to be ignored. Thanks for the tip, I will try it. If it works I guess I will make this WONTFIX (if you don't see a reasonable-to-implement workaround in the XML module), and place that tip on the apisupport release notes and manual. Could apisupport itself set this system property in restored(), or would it really need to be done earlier?
It is sampled to a static field at xml.core.XMLDataObject. I am not sure if I can guarantee that this class will be loaded after ApiSupports module installation is performed.
If workaround does not work, please reopen.
The workaround works. A little clumsy but enough for now. Thanks.
VERIFIED
*** Issue 20792 has been marked as a duplicate of this issue. ***
*** Issue 21250 has been marked as a duplicate of this issue. ***
It's important for Generic VCS filesystem, which is stored in XML file. See issue #21250 for details. As soon as looks become default, it's O.K., but they're not. The same problem happens in NB 3.3, 3.3.1. Can this be fixed?
Thank you Martin for your comment. CC'ing vcsgeneric bug's list to have ide about progress of this bug
We will not fix it. Look at Petr's comment (2002-01-16 08:57 PST), it is as designed. I think, it is wrong design of API in OpenIDE's XMLDataObject (issue #20792). You have two possibilities: (1) use Looks feature (http://xml.netbeans.org/user/faq.html#xml_faq_apisupport), or (2) disable XML modules. XML infrastructure API (issue #20532) is planned to 4.0 release, so you should decide to solve this in your side, probably by own DataObject.
None of these two posibilities are acceptable. Looks are scheduled for 4.0 and I can not force the user to uninstall XML :-( I don't think I will write a special DataObject just for purpose of storing FileSystem. This does not make sense to me, the filesystem should not be forced to do this IMHO. I'll just "wontfix" this.
Does anyone think this issue is a candidate for the keyword "RELNOTE"? Since it is a known loss of functionality affecting at least apisupport module, which will not be fixed for 3.3.x, it may deserve a mention in the release notes. I already mention it in the apisupport home page and online help, but just to be sure...
Yes. If you guys can't fix it, I suggest to mention this in Release Notes since I remember at least two external people that were confused and asked what does it mean, not counting silent users ... :-)
*** Issue 24659 has been marked as a duplicate of this issue. ***
I'm not sure I have a complete grasp on the user impact, but here's a proposed release note. Please provide additions/corrections: "In order to use the IDE's generic VCS support, API support, or other modules that make specialized use of XML in some of their files, you might have to disable the IDE's XML modules."
It is fixed for XMLs at system filesystem. Martin does it solves your issue? Then no need to mention it in release notes.
Yes, my issue is fixed. From my point of view there is nothing to be mentioned in the release notes. Thanks.
Thanks. Removing relnote keyword.
Furthermore for 3.4, apisupport no longer use XMLDO.Info at all. It creates its own data loader, just like the ant module. So it is unaffected by the XML modules - they may be on or off.
Resolved for 3.4.x or earlier, no new info since then -> closing.