Ordering Constraints for @Startup

[Steve Eynon]

I like using the @Startup annotation in my Modules for it makes my
code a lot more succinct than contributing Runnables to the
RegistryStartup service.

But when I need to order the startup method I am forced to use the
later for @Startup does not seem to take ordering constraints.

For instance, I would like to replace:

public static void
contributeRegistryStartup(OrderedConfiguration<Runnable>
configuration) {
    configuration.add("loadTraingData", new Runnable() {
        public void run() {
            trainer.load();
        }
    }, "after:ConfigSetup");
}

with

@Startup("after:ConfigSetup")
public static loadTrainingData() {
    trainer.load();
}

or even

@Startup @Order("after:ConfigSetup")
public static loadTrainingData() {
    trainer.load();
}

Any thoughts?

Steve.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org