- the factory implements a destroy method that can be used
- the resource implements Closeable then it can be closed
- an eventlistener is registered by the factory to do the cleanup
- a Runnable object is bound with JNDI name "shutdown-xxx" (and contains the shutdown code for xxx)
- configurable reflection solution
- ...
Lots of possebilities, you just have to find something that fits the general design.
Dirk
Remy Maucherat wrote:
Dirk Verbeeck wrote:
A more general solution then?
?
By definition, all resources have their own custom way of being released (hence the WONTFIX). If the JNDI interface included a "release" or something, it could possibly be made to work, but here, I don't see any way to come up with a generic solution.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
