On 11/08/2011 11:09 AM, Marlon Pierce wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Maybe jdbc:h2:/tmp/portal_data;AUTO_SERVER=TRUE would be better. Wil
have to test with Windows OS, but I assume the "/" notation is fine.
An alternative and more flexible solution might be using an Java runtime setting
(-Drave.h2.location=) and try to dynamically evaluate that from the configuration.
Then we can easily provide this location in through the maven-cargo-plugin
configuration, like ${project.build.directory}/database
This would keep the database outside the cargo tomcat deployment environment
(which gets cleared every run). Running mvn clean though would clear the
database out. Or if you don't want it, as a developer, you could redefine this
setting yourself, either from the command line or else through environment settings.
WDYT?
Marlon
On 11/8/11 12:47 PM, Jasha Joachimsthal wrote:
+1 for the combined database in the demo setup, so we can also drop
the duplicate H2 console
On 8 November 2011 18:28, Marlon Pierce<[email protected]>
wrote:
I propose that we change both the shindig and rave-portal DB
connections to jdbc:h2:~/portal_data;AUTO_SERVER=TRUE instead of
using the in-memory database.
This seems to create the DB in the user's home directory. If so:
1) Does that work on a Windows machine as well? 2) I would prefer
a temp directory over the user's home directory so Rave will not
leave files after you remove it from your machine (of course
nobody should want to remove Rave from their machine).
This will allow both rave-shindig and rave-portal to use the same
DB instance
(http://www.h2database.com/html/features.html#auto_mixed_mode).
Seems to work fine in my tests.
Marlon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOuX5mAAoJEOEgD2XReDo54qMH/RbR6oCDZ0J06L5LwyNPfM1Y
tsCu222oKWCy6NAZhvFM9ta4ram/3XiDgk2/9jpfqeHhm6uUK9ISa5T474TCOshx
07HcZQeJrOEi9Y6tN6lYqQsvrs3/VUwgGychnenmS+dtnC9rCDFSK6BPwGvRXw93
Gav2mWeImETs9RTAryYK1N3muoIWITBy8O+W8oRlcf+3O/0qB6ucStsWn8+Nr5Li
y5g+Z/I9PfnUZYEUf16GbEarZQ+Si/wB/UPzy7OsUG64bJG33zLpmNq4Vkn92oq6
DMfcdVIFn/ZS3uJifwHtRNiz8N6Su+FApizycNWS5HpF+R4GovdE43H6uKXtcjA=
=bSHt
-----END PGP SIGNATURE-----
