One step closer...
Note to self: always throw "new EJBException(ex)" and not "new EJBException(ex.toString())". Helps stack trace.
Now I get this exception line in the log file:
Looks like it's going to a Hyperion db instead of mine. Why?
Looks like it's bound to DefaultDS, if hsqldb-service.xml is any clue:
The server.log file shows
2003-01-29 16:12:56,141 INFO [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.DefaultDS] Bound connection factory for resource adapter 'JBoss LocalTransaction JDBC Wrapper' to JNDI name 'java:/DefaultDS'
Am I mapping bahiawebDB to JBoss LocalTransaction JDBC Wrapper? Back to searching for an answer.
Finally got it working. See attachment
Thanks for your info, it's been very helpful !!
I used your access datasource configuration as a sample but when i deploy it, i get a warn message:
09:41:09,699 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=pedidosDB does not implement
any Service methods
Could you post your -service.xml file?
Despite the warning i get, the datasource works fine. The only problem i have is that i have to manually start the service through the administrator.
Why is it that i don't automatically get the datasource binded to de JNDI????
Please, i need help!!
> Despite the warning i get, the datasource works fine.
> The only problem i have is that i have to manually
> start the service through the administrator.
> Why is it that i don't automatically get the
> datasource binded to de JNDI????
> Please, i need help!!
Hmm. I've never had to start the service from the console. Having the service work even though there is a warning may not mean anything. There still may be a problem in the -service.xml file that's causing your problem. Please post it.
This is the code of the file msaccess-service at
I took the file from the examples directory, so it should work correctly.
<config-property name="ConnectionURL" type="java.lang.String">jdbc:odbc:pedidosDB</config-property>
<config-property name="DriverClass" type="java.lang.String">sun.jdbc.odbc.JdbcOdbcDriver</config-property>
jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
Well, you were right, the service file works fine. I looked through my log files, and my service file gives the same message.
So you say that the service has to be started through the admin console, right? What error message did you get when you didn't do that?
I had no error message.
When requesting a secured page, no matter what login/password y entered, nothing happened. It just wasn't getting the connection to de datasource.
Now, i changed my JBoss to 3.0.4 and eveything works fine. Only God kowns why.
Best of luck, then!