I think the log you show indicates that the datasource is successfully deployed and bound in jndi. Check in jndi view to see what it is bound under. Check the connectionfactoryloader mbean (not the jsr-77 one) to make sure all the properties are as you expect and that it is started.
I think there is a naming problem, which I usually get confused with. Have you tried java:/resnet?
Thanks for the quick reply. Using java:/resnet in the jbosscmp-jdbc works for the entity beans :).
I still cannot find the datasource with a straight JNDI though, if I do:
Hashtable props = new Hashtable();
Context ctx = new InitialContext(props);
Object obj = ctx.lookup("resnet");
I get javax.naming.NameNotFoundException: resnet not bound
I've also tried java:/resnet, java:comp/env/resnet and any other combination i could think of.
In the jboss.jca:service=ConnectionFactoryLoader,name=resnet the JndiName has the value resnet so I do not understand why i cant find such an object in JNDI bound as resnet. I must be missing something.
Any ideas would be much appreciated.
Since you are trying to set props for your initial context, maybe you are trying to get the datasource from another vm. YOU CANT, STOP TRYING. The java: namespace is accessible only from in-vm. I assume you know about jndiview accessible on port 8082?
Oh, I didn't know that. This explains why my Junit tests are failing even though it actually works. I'll switch to Cactus for those tests instead. Thanks for the information :)