I have a current project that I am VERY close to converting all it's code from core servlets to t5.2.6. But I have this project split to a jar file containing most of the business logic, servicec, dao, etc.
After intergrating this jar into the tapestry project, I need to start some services and shut them down when I'm done. For startup I use the *@Startup* annotation to mark a *static void* method which runs a thread, initializing my services. About shutdown I found very nice information on this page: https://cwiki.apache.org/confluence/display/TAPESTRY/Tapestry+Inversion+of+Control+FAQ But this implies carrying tapestry IoC jar along with my jar (because services are annotated with tapestry IoC annotations) even in an environment that doesn't use tapestry's IoC. I just don't wan't my jar to be tapestry dependent just to separate the presentation layer from anything else. So is ther a *@Shutdown* annotation just like the *@Startup* one ? This is will mirror perfectly to the *contextInitialized* and * contextDestroyed* methods implemented in context listeners usually implemented for the same purpose in core servlets projects. -- *Regards,* *Muhammad Gelbana Java Developer*
