data-source for default derby maildb is configured with a relative path

• Key: JAMES-527
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Norman Maurer
• Reporter: Joachim Draeger
• Component/s: James Core
• Affects Version/s: 2.3.0, 3.0
• Fix Version/s: 2.3.0

Description

Data source is configured with a relative path in config.xml:

         <dburl>jdbc:derby:../apps/james/var/derbydb;create=true</dburl>

The path is relative to the current directory when starting james. Calling run from the bin folder is allright. Calling it from James root directory bin\run.bat causes the db to be created in the uplevel directory.

Possible solutions:

 - add a "cd PHOENIX_HOME" in start scripts
 - evaluate the PHOENIX_HOME enviroment variable in James

Comments

Now we change to $PHOENIX_HOME/bin before start james. This seems to me a better solution then use getProperties() at the moment. Anyway we should maybe change the config for not using a relative path on derby configuration.

[Stefano Bagnara]

Still there in Windows.

[Joachim Draeger]

Other directories in var don't seem to be accessed by a relative path, how is it managed there?
Although the cd fix is okay for now it is IMHO odd to use relative path in the James enviroment by default.

What do you think?

   - reopen as improvement?
   - create new?
  - it's okay the way it is?

[Danny Angus]

Closing issue fixed in released version.