First 3.2 implements jca1.0
Second, do you see a message saying the jar is being deployed?
You might need to enable debug logging
(change the level for org.jboss to DEBUG in conf/log4j.xml)
then look in log/server.log
to see what is happening during the deployment.
thanks for your response.
I checked the JCA spec 1.0, section 10.2
RAR packaging guidelines are the same. (ie, I just need to package all necessary JAR files into the RAR file)
I did change the log level and looked into server.log.
Here is what I see during the adapter deployment:
2004-01-07 18:33:16,064 DEBUG [org.jboss.resource.RARDeployer] looking for nested deployments in : file:/C:/jboss-3.2.3/server/default/deploy/joe_adapter.rar
2004-01-07 18:33:16,074 INFO [org.jboss.resource.RARDeployer] nested deployment: file:/C:/jboss-3.2.3/server/default/tmp/deploy/tmp21797joe_adapter.rar-contents/ra.jar
2004-01-07 18:33:16,085 INFO [org.jboss.resource.RARDeployer] nested deployment: file:/C:/jboss-3.2.3/server/default/tmp/deploy/tmp21797joe_adapter.rar-contents/cci.jar
And subsequent lines indicate that ra.jar and cci.jar were deployed without any error.
Also, using the JMX console I invoked getPackageClassLoaders, and found that both my package names (joe.adapter.connection and joe.adapter.cci) are loaded by UnifiedClassLoader3@1bbbafc
PS: My JBoss version is 3.2.3..
Post the exception stacktrace where you have the problem.
Enable the classloader trace logging mentioned in the classloader docs
to see whether you can workout why it is not finding the class.
Finally, post an example that reproduces the problem as a bug