Do you have the right version of oracle-service- jboss3alpha needs one with "mbean-ref" rather than "depends" tags.

Also chech the object names in these tags are the same as the object names of the mbeans referenced. (especially the mbean domain, e.g. jboss.jca: vs. JCA:)

Read the log carefully to find out what is going wrong, check the port 8082 stuff to see what is started.

FWIW, I am having the same problem with a SQL Server DS. Autodeployer finds the service xml and seems to deploy it OK, except the name never gets bound in JNDI. WIth the Hypersonic DS, there is a line in the log that says explicitly that the datasource name was bound - not so with the MS one. In JNDIView, Hypersonic is there (DefaultDS), but SQL Srvr one isn't.

From the log:
[11:18:37,249,AutoDeployer] Auto deploy of file:/D:/jboss/jboss-3.0.0alpha/deploy/mssqlds-service.xml
[11:18:37,319,Default] Libraries adding URLClassLoader -861013034 key URL file:/D:/jboss/jboss-3.0.0alpha//lib/ext/msbase.jar
[11:18:37,339,Default] Libraries adding URLClassLoader 657315836 key URL file:/D:/jboss/jboss-3.0.0alpha//lib/ext/mssqlserver.jar
[11:18:37,339,Default] Libraries adding URLClassLoader 1590486151 key URL file:/D:/jboss/jboss-3.0.0alpha//lib/ext/msutil.jar
[11:18:37,339,ServiceCreator] About to create the beanjboss.jca:service=ConnectionFactoryLoader,name=MSSQL2000DS
[11:18:37,349,ServiceCreator] Created the beanjboss.jca:service=ConnectionFactoryLoader,name=MSSQL2000DS
[11:18:37,550,AutoDeployer] Started

TIA,
Mike

It's fixed. The problem was an embedded in the mbean-ref for ResourceAdapterName. The name value within the element was:
"Minerva JDBCLocalTransaction ResourceAdapter"
instead of
"Minerva JDBC LocalTransaction ResourceAdapter"

The symptoms were that the service would be deployed, but no JNDI name would be bound for the data source. Fallout from copy/paste I suppose.