As the name suggests, org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl is an
XADataSource, not a DataSource. Why does Castor need to know the
implementation class of the DataSource interface? What happens if you just
say javax.sql.DataSource? What's the config you are setting?
java:/MSSQLDS should be a DataSource.
You may be getting class cast exceptions because JBoss has its own
definitions for j2ee classes, I think including DataSource. If Castor also
includes a definition try removing it.
david jencks
On 2002.04.25 11:49:32 -0400 "Tse, Leo" wrote:
> Hello,
>
> I like to know if anyone is using
> "org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl" as their
> DataSourceClass
> when using Castor with a connection pool.
> I'm trying to do so, and it seems like my connection pool is up and
> running(
> as seen when I run the JBoss)
> and I can see the DataSource being binded on port 8082 and jndi view
>
> but I get the following exception when I try to get the database with the
> JDO:
>
> [test] org.exolab.castor.jdo.DatabaseNotFoundException: The JNDI name
> java:/MSSQLPool does not map to a JDBC DataSource
> [test] org.exolab.castor.mapping.MappingException: The JNDI name
> java:/MSSQLPool does not map to a JDBC DataSource
> [test] at
> org.exolab.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.
> java:310)
> [test] at org.exolab.castor.jdo.JDO.getDatabase(JDO.java:559)
>
> Any suggestions would be great!
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
>
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
