Re: [xml-dev] module loader dependent on XMLDataObject

On Fri, 07 Mar 2003 20:58:28 +0100, Petr Kuzel <[email protected]>
wrote:

>That's fine to have separate data loader. XMLSchema and XSL
>data objects use the same approach. I has two advantages
>and one disadvantage:
>  + user can change loaders order under options : object types
>  + XML core module need not to contain secondary
>    classifier (loader) subsystem and its UI (the options)
>  - every new subtype requires extra classes (invalid
>    once DataLoader would not be required to be a singleton)
>  [Jesse could extend it :-)]  
>

How can I enforce a loader order at module-install time?  I just
installed my GrXML module, and it had the XMLDataLoader's set of
actions until I went to options : object types and moved the GrXML
loader up above the generic XML entry.

My manifest currently looks like:

Name: com/nuance/tools/grxml/GrXMLDataLoader.class
OpenIDE-Module-Class: Loader
Install-Before: org.netbeans.modules.xml.core.XMLDataObject

which used to do the trick in 3.4.1.

Thanks,
Rich