java从外部得到数据,从Web容器外部访问数据源（通过JNDI）

I'm trying to access a data source that is defined within a web container (JBoss) from a fat client outside the container.

I've decided to look up the data source through JNDI. Actually, my persistence framework (Ibatis) does this.

When performing queries I always end up getting this error:

java.lang.IllegalAccessException: Method=public abstract java.sql.Connection java.sql.Statement.getConnection() throws java.sql.SQLException does not return Serializable

Stacktrace:

org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.doStatementMethod(WrapperDataSourceS

ervice.java:411),

org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.invoke(WrapperDataSourceService.java

:223),

sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source),

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25),

java.lang.reflect.Method.invoke(Method.java:585),

org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155),

org.jboss.mx.server.Invocation.dispatch(Invocation.java:94),

org.jboss.mx.server.Invocation.invoke(Invocation.java:86),

org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264),

org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659),

My Datasource:

jdbc/xxxxxDS

jdbc:oracle:thin:@xxxxxxxxx:1521:xxxxxxx

false

oracle.jdbc.driver.OracleDriver

xxxxxxxx

xxxxxx

org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter

5

20

Does anyone have a clue where this could come from?

Maybe someone even knows a better way how to achieve this.

Any hints are much appreciated!

Cheers,

Michael

解决方案

@Michael Well, java.sql.Connection is an Interface - it might technically be possible for the concrete implementation you're getting from JBoss to be Serializable - but I don't think you're really going to have any options you can use. If it was possible, it would probably be easy :)

I think @toolkit might have said the right words with useable outside the VM - the JDBC drivers will be talking to native driver code running in the underlying OS I guess, so that might explain why you can't just pass a connection over the network elsewhere.

My advice, (if you don't get any better advice!) would be to find a different approach - if you have access to locate the resource on the JBoss directory, maybe implement a proxy object that you can locate and obtain from the directory that allows you to use the connection remotely from your fat client. That's a design pattern called data transfer object I think Wikipedia entry