Hello, I'm currently looking at a strange problem. Every module method annotated with @Startup (from all available modules, for example also JpaModule#startupEarly) are being executed twice under certain circumstances. After some decent debugging I found this out:
The app is started, registry is up and no app specific service has been called or realized. As soon as the first service is realized that uses any contributions there's some kind of lookup going on. The appropriate contribute***myService*** methods are called from the modules (I've got a multi module project here). Within the same lookup process all methods annotated with @Startup are called as well. As if they would be part of the ordered configuration or something. I'm pretty sure there's something's wrong with the @Startup code. RegistryImpl#addToOrderedConfiguration is called when realizing that one (I think only the first) service with an ordered configuration... and that call makes the extra startup-invocations. ...Or are there any known bugs that I'm not aware of and that's totally normal? Best Christian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
