Connector access via JNDI?

Question

I have a project on java.net - https://lucenerar.dev.java.net/ if you're interested - and I have a client class meant to hide all the JNDI and connector plumbing from my application. However, this class needs to look up the connector via JNDI.
This is all fine and good, but my webapp fails verification in the J2EE 1.4 RI if I have a resource-ref to a Connector factory. According to the developer's guide at http://docs.sun.com/source/819-0079/dgjndi.html I should be able to specify a resource of type javax.resource.cci.ConnectionFactory - which I do! - but this is the only cause of failure I can find.
Note that I don't have a sun-web.xml yet, so it may be that it's trying to resolve the local name to a global name, and failing at that point. If that's the case, it's an error on my part as deployer, which I'll be glad to address - but I'd really rather know if that's actually the cause of my error, because that SHOULD be something I can configure at deploy-time rather than build time, IMO (as the connection factory's name is configured at deploy-time rather than build-time.)
Does anyone see anything obvious that I'm doing incorrectly?

Answer 1

[#|2005-01-20T19:59:00.836-0500|INFO|sun-appserver-pe8.1|javax.enterprise.system.tools.verifier|_ThreadID=24;|INFO: Look in file "/var/tmp//main-site.war20050120075858.txt" for detailed results.|#]
[#|2005-01-20T19:59:03.214-0500|INFO|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=25;|Total Deployment Time: 30206 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2005-01-20T19:59:03.257-0500|SEVERE|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=25;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Some verifier tests failed for the given application. Aborting deployment. Please verify your application using the verifier separately for more details
     at com.sun.enterprise.deployment.backend.ModuleDeployer.runVerifier(ModuleDeployer.java:871)
     at com.sun.enterprise.deployment.backend.WebModuleDeployer.preRedeploy(WebModuleDeployer.java:260)
     at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:160)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:188)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:520)
     at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143)
     at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:171)Looking at the text file yields:
      FAILED TESTS :
      Test Name : tests.web.WebResourceType
      Test Assertion : The resource-type element specifies the Java class type of the data source. Please refer to Java Servlet 2.4 Specification Section #SRV.13.4 for further information.
      Test Description : For [ main-site.war ]
Error: The resource-type [ javax.resource.cci.ConnectionFactory ] element does not specify a valid Java class type for the data source within Web application [ main-site ].This is the failure that prevents deployment, that I'm trying to resolve. My suspicion is that my connection factory doesn't implement something it's supposed to, but I don't know where to look to find out what it is. SRC.13.4 sheds little light on it.