Hi Francis,

first of all we're happy that we have you now on the project and to find you so 
keen on improving the project.

Creating a branch is certainly a good idea. There are (as far as I know) 
currently only minor bugfixes going on and it should be fairly simple to merge 
the branches later on.

As far as your problem with loading the config.xml is concerned, it is no 
problem to change the Sample Application's code. Currently it is assumed that 
by default the config.xml can be found in the current directory which is the 
project's root directory in Eclipse.

We should however give a hint if the config.xml cannot be found and the thus 
the hard coded default are being used, which was the problem in your case. I 
have now corrected the SampleAdvConfig defaults as a first step. 

Since I am a little busy at the moment I might not always be able to reply 
straight away, but I will try my best.

Regards,
Rainer


francisdb commented on EMPIREDB-31:
-----------------------------------

it's the defaults in SampleAdvConfig.java that are wrong, I suppose I was not 
using the config.xml

> advanced sample throws SQLException (wrong db user)
> ---------------------------------------------------
>
>                 Key: EMPIREDB-31
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-31
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>            Reporter: francisdb
>            Assignee: Rainer Döbele
>
> running the advanced example gives me:
> java.lang.RuntimeException: java.sql.SQLException: User not found: 
> JDBC:HSQLDB:FILE:HSQLDB/SAMPLE;SHUTDOWN=TRUE
> this is because SampleAdvConfig has the wrong value as user:
> is:
> private String jdbcUser = "jdbc:hsqldb:file:hsqldb/sample;shutdown=true";
> should be:
> private String jdbcUser = "sa";
> (I filed this issue before for the main example project, but it seems the 
> advanced example has the same problem)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Reply via email to