We could possibly do some work so that the necessary locks are only locked after the "will-shutdown" listeners are notified, but before the "did-shutdown" listeners are notified.
On Thu, Dec 20, 2012 at 4:50 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Thu, 20 Dec 2012 20:24:54 -0200, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > No it's not >> >> binder.bind(ISCMailer.class, SCMailerImpl.class); >> > > Try binder.bind(ISCMailer.class, SCMailerImpl.class).eagerLoad(**); It > seems your service wasn't used nor reallyl instanced (Tapestry services are > proxied, so only the proxy is created at first, with the real service > instance created on demand) before the registry shutdown, so Tapestry ends > up attempting to instance it when the registry is already shutting down. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
