Can get work the attribute "destroy-method".

First, even if I type non-existing method name into "destroy-method" attribute,

Spring initialization completes fine (already strange!).

Next, when a bean has a "prototype" scope, then I suppose it must be destroyed before the application

is closed. That not happens, it is simply never called in my case.

Though, after extracting this bean I can call this method explicitly and it does its job.

Could you explain why this method is never called in my Spring 2.5 case?

p.s. The method exists, it is public and has no arguments.

It seems to be a more difficult task then I thought.

The problem is that this destroy method is called whenever the context is closed, and this is a rare case.

My question is this:

I can do it by hand, but is there any solution how to make Spring do this job? It destroys the bean after the session is destroyed, it might be possible for Spring to call a method on that bean before destroying it?