Sebastien Arbogast wrote:
2005/5/26, Siegfried Goeschl <[EMAIL PROTECTED]>:
I'm also not a Spring expert - actually I never used it - but
+) you might be able to derive from
org.apache.commons.dbcp.BasicDataSource and overwrite the
close() method
I like this one but I can't figure out how I can access my database
from there to send the SQL instruction (I'm not an expert with dbcp at
all).
+) add a custom HSQLDB shutdown bean for Spring
+) or write a little servlet which does the magic
Why not but haven't a clue about how to do that.
Would it be a good approach to use an AOP approach :
- you create an aspect that will add behaviour to the close() method of
your dataSource bean.
Technically that would be the most elegant solution even if I've never
used AOP. But there is another problem here : all my Spring files are
automatically generated through a MDA process (AndroMDA) and I'm quite
sure I can't integrate AOP in the process.
You can easily use AOP with MDA, I use aspectj with my AndroMDA apps all
the time, because your system is generated does not mean you can't
introduce aspects into the process.
I think the most pragmatic solution right now would be to customize
the close method of my BasicDataSource. But the question is : can I
access my JDBC connection from there to issue my SHUTDOWN ?
(Why did they introduce that SHUTDOWN thing anyway ?!!! grrrrrr...)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
