User Story #138 (closed)
Improper setting of database URI
| Reported by: | anonymous | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M2 |
| Component: | Deployment | Keywords: | iteration2 |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Currently the "java omero setup" Ant task does not properly set the hibernate.connection.url. It appears to use the application server host instead of the database host.
Change History (7)
comment:1 Changed 13 years ago by cxallan
comment:2 Changed 13 years ago by cxallan
etc/local.properties file:
#
# This file was generated by the configure task at 20060530 1303
#
server.host=localhost
server.port=1099
omero.user=callan
omero.pass=${config_omero.pass}
hibernate.connection.username=callan
hibernate.connection.password=secret
database.host=warlock
database.name=omero3
#
# postgres profile
#
hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect
hibernate.connection.driver_class=org.postgresql.Driver
hibernate.connection.url=jdbc\:postgresql\://warlock/omero3
Replaced the ${config_hibernate.connection.password} in the hibernate.connection.password property with "secret" and things appear to work.
What's the story with this whole thing?
comment:3 Changed 13 years ago by jmoore
This is actually a bigger Java PITA. The comments in setup.xml give the fuller story. See:
http://issues.apache.org/bugzilla/show_bug.cgi?id=33354
Basically, you have to manually set the user passwords because there's no way to turn off character echoing.
Perhaps we should change that default value to: CHANGE_ME. Agree?
comment:4 Changed 13 years ago by jmoore
r694 adds CHANGE_ME. Closeable, or is it still tricky on new/old checkouts?
comment:5 Changed 13 years ago by cxallan
What about the original issue? (The improper setting of hibernate.connection.url)
comment:6 Changed 13 years ago by anonymous
- Resolution set to fixed
- Status changed from new to closed
Tricky but closed by r696.
Scopes are a known issue in ant. (1.7 might bring some new hope.) What was happening is that setup.xml was essentially trying to redefine a property value through a couple layers of re(mis-)direction. This un-redefined value was then being passed along.
comment:7 Changed 13 years ago by jmoore
- Keywords iteration2 added
- Milestone changed from Unscheduled to cycle1
- Version changed from 3.0-M2 to 3.0-M1
Further, I'm having issues running itests now:
Am I just doing something wrong here? Missing some config?