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.
Currently it supports just Environment attaching by DOCTYPE public ID. It is unfortunate because some XML documents such as Ant scripts (and all future document using XML Schema) cannot use this feature. Attaching based on MIME type sounds like a definite solution. I.e. scan system/xml/environment/${MIMEName} for Enviroment.Providers.
I will take care of it, if nobody objects.
This would be enough for the Ant module to at least coexist peacefully with the XML module. Does not take care of switching Ant's XML structure handling, but that can be done separately I think.
My latest understanding of loaders.XMLDataObject is that it primary handles system XML files. All user XML files should be handled by particular modules (Ant, Generic XML, XSLT, Schema, ...) using XML tools API. We need to define XML related cookies rather that require modules handling user XML files to rely on/subclass support for system XMLs.
Agreed that that is a good goal.
Set target milestone to TBD
Petr have you get rid of XMLDataObject in new datasystems API? It's not b/c change so it is probably right time to perform it now in 4.0 timeframe.
I guess this would be a non-issue in DS II - you already support adding lookup cookies and looks generally by MIME type, which is all this is asking for.
I cannot find particular DS ?? issue to establish dependencies/duplicate it.
I don't think there is a specific issue filed yet.
Agree with Jesse, but have nothing against leaving this issue open. Some info can be found at <http://openide.netbeans.org/proposals/fsextension/design.html>
ant is not the issue, it has own loader. I do not know anything about schema. Moreover we survived few years without these changes, I am sure we can survive few more.