[jboss-jira] [JBoss JIRA] Created: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined

Shelly McGowan (JIRA) jira-events at lists.jboss.org
Wed Feb 16 19:39:13 EST 2011


Resource adapter deployment fails when an authentication-mechanism-type is defined
----------------------------------------------------------------------------------

                 Key: JBAS-8894
                 URL: https://issues.jboss.org/browse/JBAS-8894
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Shelly McGowan


The the authentication-mechanism element of the ra.xml is used to specify the authentication mechanism supported by the resource adapter.  If the authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
         <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
         <credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>

19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of deployment "jbosstestadapter.rar"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
	at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
	at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
	at org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
	... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of javax.resource.spi.security.PasswordCredential; org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
	at org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
	at org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
	at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
	at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
	at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
	at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
	at org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)

The deployment does succeed if the authentication-mechanism element is empty.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list