Would you believe I was just looking into that over the weekend?
Substitute Tomcat for Jetty, though.
The solution I initially came up with -- and their might be a better way
-- is to add some <property> tags in the .application file to specify
the path/etc (basically, any custom configuration key/value pairs).
Then you can read the property and set the connection dictionary/etc.
I was going to post the Tapestry-specific code bits to the tapestry-user
mailing list, but I can include it here, too, if anyone else is
interested. I haven't gotten to the point yet of setting the connection
dictionary, but that's pretty easy once you have the values.
/dev/mrg
PS. I'm also leaning towards running HSQLDB in server mode from within
the Tapestry application, so I can still access it (the database) while
the application is running. Just a thought for you.
-----Original Message-----
From: Kevin J. Menard, Jr. [mailto:nirvdru..egativetwenty.net]
Sent: Tuesday, October 26, 2004 10:10 AM
To: cayenne-use..bjectstyle.org
Subject: HSQLDB standalone in webapp?
Hi,
I'd like to make a wholly contained webapp. With Tapestry, Cayenne,
and Jetty, things have generally been going well. To really make it
wholly contained, I was looking to switch to HSQLDB, but can't seem to
figure out how to run it in standalone mode with a directory relative
to the webapp. Anyone out there have any thoughts on the matter?
Thanks,
Kevin
This archive was generated by hypermail 2.0.0 : Tue Oct 26 2004 - 10:18:20 EDT