Greetings,

We have an application that used to work with Orion 0.9.4 and
breaks under 1.0rc1.

In 0.9.4 the java.sql.DataSource implementation returned from
JNDI is com.evermind.server.ejb.EJBDataSource.  In 1.0rc1 this
changed to com.evermind.sql.OrionCMTDataSource.  Our application
calls the getConnection() method on whatever is returned, and
then calls prepareStatement() on the connection instance.  In
1.0rc1 this fails with a NullPointerException.  Here's the
relevant part of the stack trace:

java.lang.NullPointerException
        at com.evermind.sql.OrionCMTDataSource.c7(JAX)
        at com.evermind.sql.OrionPooledDataSource.cw(JAX)
        at com.evermind.sql.OrionPooledDataSource.cw(JAX)
        at com.evermind.sql.ah.da(JAX)
        at com.evermind.sql.ah.dc(JAX)
        at com.evermind.sql.am.prepareStatement(JAX)
...

The configuration of the data source in data-sources.xml is the
same under both 0.9.4 and 1.0rc1:

        <data-source
                name="Some data-source"
                class="com.evermind.sql.ConnectionDataSource"
                location="jdbc/ssp/Stash"
                ejb-location="jdbc/ssp/Stash"
                xa-location="jdbc/xa/ssp/Stash"
                url="jdbc:rmi://localhost:1099/jdbc:cloudscape:StashDB"
                connection-driver="RmiJdbc.RJDriver"
                username=""
                password=""
        />

Another point that might be of interest is that the connection
object under 0.9.4 has a name that looks "resolved", i.e. has
jdbc:rmi://localhost:1099/jdbc:cloudscape:StashDB in it, while
in 1.0rc1 its name is jdbc/ssp/Stash, the string used to look it
up via JNDI.

We would be very happy if someone with access to the source could
take a look at this.

Thanks,

Dejan Vucinic
[EMAIL PROTECTED]

Reply via email to