thanks thiago, that would work too... however if using a embedded hsqldb
in production the same problem would occur...
in order to solve my case, it's probably simpler to just create a new
jdbc connection for shutdown (without hibernate support).
however i'm intrigued that there's no ability to do cross-service
shutdown within tapestry-ioc?
shall i rephrase the question to
"how do i reference Service A when shutting down Service B" ?
I can see that this would be a reasonably common issue for people and am
surprised it's not possible...
p.
On 29/11/2010 10:22 PM, Thiago H. de Paula Figueiredo wrote:
On Mon, 29 Nov 2010 03:28:09 -0200, Paul Stanton <[email protected]>
wrote:
Hi all,
Hi!
I'm using tapestry-hibernate and an embedded HSQLDB database.
Another suggestion: why don't you use a non-embedded HSQLDB database
while developing? That's what I do when I use HSQLDB. Or launch a
thread that sends the "checkpoint" command to HSQLDB every n seconds.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
