XESame and Derby

SunnyOz

Hi there,

I was wondering if XESame can be directly connected to a derby database?
The settings I use work fine for SQirreL but seem to cause an authentication error in XESame.
A mapping extract of my connection:
<connection>
    <columnSeperatorStart>[</columnSeperatorStart>
    <columnSeperatorEnd>]</columnSeperatorEnd>
    <URL>jdbc:derby://localhost:1527/entityDB</URL>
    <driver>org.apache.derby.jdbc.ClientDriver</driver>
    <driverLocation>/usr/share/javadb/lib/derbyclient.jar</driverLocation>
    <properties>
      <java.util.AbstractMap_-SimpleEntry>
        <key class="string">username</key>
        <value class="string">app</value>
      </java.util.AbstractMap_-SimpleEntry>
      <java.util.AbstractMap_-SimpleEntry>
        <key class="string">password</key>
        <value class="string">app</value>
      </java.util.AbstractMap_-SimpleEntry>
      <java.util.AbstractMap_-SimpleEntry>
        <key class="string"></key>
        <value class="string"></value>
      </java.util.AbstractMap_-SimpleEntry>
    </properties>
    <description>DEFAULT connection to an ODBC source, please change to your situation</description>
  </connection>

Any help is much appreciated.

Thanks, SunnyOz

JBuijs

Dear SunnyOZ,

What you could try is to remove the properties 'username' and 'password' (just empty all fields) and put them in the URL which would then become something like:
jdbc:derby://localhost:1527/entityDB;user=jill;password=toFetchAPail (from this article)

Let me know if this works!

SunnyOz

Hey Joos, awesome! That works. Btw. I couldn't find any documentation about how to use XESame with other database interfaces but ODBC. Perhaps you should update your documentation.

Thanks!

JBuijs

Hey SunnyOz,

I'm glad to hear that it works.

XESame requires a JDBC connection to the datasource. Since all JDBC connections are set up in a similar way, sometimes to an ODBC connection using a JDBC-ODBC bridge, there is only one description necessary. Driver specific things are best found in their documentation.

I agree with you that XESame could use some more documentation but as you know, bug fixing and feature extension has a higher priority.