My core module shuts down 2 database services but I recently deployed a new application that uses only one schema so when the *RegisteryShutdownHub *service calls the shutdown procedure, the idle database connection service is asked to shutdown by calling *.close()* and this attempts to instantiate it, which fires an exception because the registry is shutting down already.
This obviously can be addressed in many ways and I've already solved it but I suppose this is still a good addition. I think if someone, just might use it for any reason whatsoever, this might give Tapestry the edge over other frameworks after all. *---------------------* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana On Mon, Oct 14, 2013 at 2:31 PM, Lance Java <lance.j...@googlemail.com>wrote: > The Scoreboard is a ServiceActivityTracker. I've never needed to do it > myself but I'm sure you can register your own custom tracker. > On 14 Oct 2013 13:17, "Martin Kersten" <martin.kersten...@gmail.com> > wrote: > > > Sometimes it is very important. I for myself need this in some tests to > > recognize some specials in tear down and set up. And thanks Lance for the > > hint. I used another way but this Scoreboard is way more cooler. Wasnt > > aware of this. > > > > > > 2013/10/14 Thiago H de Paula Figueiredo <thiag...@gmail.com> > > > > > On Sun, 13 Oct 2013 12:14:46 -0300, Muhammad Gelbana < > > m.gelb...@gmail.com> > > > wrote: > > > > > > Will many agree with me if I asked for a way to safely check if a > > service > > >> has been initialized or built ? > > >> > > > > > > Why do you need that? If you invoke a service method, the service will > be > > > initialized and ready to use, even if Tapestry-IoC has to initialize it > > in > > > the spot. In another words, if you're using a Tapestry-IoC service, you > > can > > > always assume it's ready to be used. > > > > > > -- > > > Thiago H. de Paula Figueiredo > > > Tapestry, Java and Hibernate consultant and developer > > > http://machina.com.br > > > > > > > ------------------------------**------------------------------**--------- > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org< > > users-unsubscr...@tapestry.apache.org> > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > >
