[AMQ-9398] Fix Jakarta EE 10 support via xml wiring for activmeq-ra

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 6.0.1
• Component/s: RAR
• Assignee: Matt Pavlovich
• Reporter: Matt Pavlovich
• Created: 21/Nov/23 16:37
• Updated: 29/Nov/23 20:38
• Resolved: 22/Nov/23 12:59

Description

I did a simple test by placing the files in the deployments directory on a Wildfly 28 server (since that is how the resource adapter is deployed on my older Wildfly server) but I got the following errors:
2023-11-21 10:08:21,890 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "activemq-rar-6.0.0.rar" (runtime-name: "activemq-rar-6.0.0.rar")
2023-11-21 10:08:23,425 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."activemq-rar-6.0.0.rar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."activemq-rar-6.0.0.rar".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "activemq-rar-6.0.0.rar"
at [e-mail]//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1590)
at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1553)
at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1411)
at [e-mail]//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at [e-mail]//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at [e-mail]//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at [e-mail]//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0043: Failed to parse service xml ["/content/activemq-rar-6.0.0.rar/META-INF/ra.xml"]
at [e-mail]//org.jboss.as.connector.deployers.ra.processors.RaDeploymentParsingProcessor.process(RaDeploymentParsingProcessor.java:123)
at [e-mail]//org.jboss.as.connector.deployers.ra.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:91)
at [e-mail]//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)

... 8 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of jakarta.resource.spi.security.PasswordCredential; org.ietf.jgss.GSSCredential;jakarta.resource.spi.security.GenericCredential
at [e-mail]//org.jboss.jca.common.api.metadata.spec.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parseAuthenticationMechanism(RaParser.java:1451)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parseOutboundResourceadapter(RaParser.java:1308)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parseResourceAdapter(RaParser.java:868)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parseConnector15(RaParser.java:360)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parse(RaParser.java:173)
at [e-mail]//org.jboss.jca.common.metadata.spec.RaParser.parse(RaParser.java:86)
at [e-mail]//org.jboss.as.connector.deployers.ra.processors.RaDeploymentParsingProcessor.process(RaDeploymentParsingProcessor.java:114)
... 10 more

When looking inside ra.xml I see several references to javax classes (e.g. javax.resource.spi.security.PasswordCredential). According to earlier answers, the next release of ActiveMQ 5.x should have full jakarta support, including the resource adapter. Is this still true or have there been some change in planning? Or do I need to do something else to be able to use the resource adapter?