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 we have two almost independent supports for XSL files: - similar code in loaders, data objects, nodes, resolvers ... - we have load some parts of this infrastructure in every IDE session (loaders/resolvers) so this has impact on startup time, memory footprint, data object recognizing
Actually, they are not independent. Our editor extends the functionality provided by standard one. Also our XSL support is tightly bound to our project type, while standard one works with any arbitrary project type: -Standard loader checks only file extension, our loader check project context and load metadata from other project files. -Data objects have some extra items in lookup(required by our editor) and provide completely different implementation of editor support. -Node was added to be able to have an icon, different from default and to be able to add some project-specific actions in future. Also, keep in mind that standard editor is a part of basic installation, while our editor only comes with SOA functionality pack. Starting from next release we may have different development cycles and schedules. So, it would be nice to keep pure modular structure here rather than put everything in one module. BTW, We have a feature request to make our, mapper-based, editor to be able to edit XSL files in other project types(see IZ95642). To do so we should first find out where to persist mapper metadata(about schema types used for target and source documents). When we do this we can completely replace current XSL support with ours, but we don't have resources to implement this in current release.