Where do I have to register the Adapter in JNDI

[tomheisner]

Hi,

I have a sample Resource Adapter (The javaworld example by dirk reinshagen at http://www.javaworld.com/javaworld/jw-02-2002/jw-0201-jca2_p.html).

The rar-File contains the ra.xml and the myjca.jar. I got it deployed but I can't lookup the thing. My Question: where do I have to register the adapter to the JNDI??
I also have the myjca-service File in the deploy directory.

The sample contains a weblogic-ra.xml file. What is the equivalent for JBOSS??


Thanks for your help.


Tom


BTW:
This is the output of JBOSS:

16:27:39,576 INFO [MainDeployer] Starting deployment of package: file:/C:/Downloads/Software/jboss-3.0.0_tomcat-4.0.3.zip/jboss-3
.0.0_tomcat-4.0.3/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/myjca-service.xml
16:27:39,776 INFO [RARDeployer] Creating
16:27:39,776 INFO [RARDeployer] Created
16:27:39,776 INFO [RARDeployer] Starting
16:27:39,786 INFO [MainDeployer] Adding deployer: org.jboss.resource.RARDeployer@3e926
16:27:39,786 INFO [RARDeployer] Started
16:27:39,786 INFO [MainDeployer] Successfully completed deployment of package: file:/C:/Downloads/Software/jboss-3.0.0_tomcat-4.0
.3.zip/jboss-3.0.0_tomcat-4.0.3/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/myjca-service.xml
16:27:39,786 INFO [MainDeployer] Starting deployment of package: file:/C:/Downloads/Software/jboss-3.0.0_tomcat-4.0.3.zip/jboss-3
.0.0_tomcat-4.0.3/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/myjca.rar
16:27:40,016 WARN [ServiceController] jboss.jca:service=RARDeployment,name=MyConnector does not implement any Service methods
16:27:40,036 INFO [MainDeployer] Successfully completed deployment of package: file:/C:/Downloads/Software/jboss-3.0.0_tomcat-4.0
.3.zip/jboss-3.0.0_tomcat-4.0.3/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/myjca.rar


and the exception thrown by the testclient:

Received initial Context
javax.naming.NameNotFoundException: MyConnector not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:445)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429)
at javax.naming.InitialContext.lookup(Unknown Source)
at Client.init(Client.java:44)
at Client.main(Client.java:79)

[davidjencks]

The myjca-service.xml file is more or less equivalent to the weblogic file you mention. You don't show it or anything about its deployment so there isn't any way to guess what might be wrong. I'd recommend using a more recent jboss version than 3.0.0.