Overriding the filter might look ugly, but it was designed for that; see
the comments on destroy() and destroy(Registry registry).
You might find it less ugly to have a ServletContextListener and do the
cleanup in contextDestroyed.
The real solution would be to have a registryIsShuttingDown()
notification, fired before registryDidShutdown(). I haven't found it,
though.
El 29/11/10 12:53, Tom van Dijk escribió:
Which service would that be? Could you provide a stack trace?
Perhaps you could make your service contribute to RegistryStartup as well,
to make sure the DbShutdownImpl service is realized and that the
sessionSource is realized. The "startupService" would then be the registry
startup method.
I agree that modifying TapestryFilter is an ugly solution and should be
avoided if possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
