[jboss-jira] [JBoss JIRA] (WFLY-4919) Jandex backward compatibility issue

[Alessio Soldano (JIRA)]

Alessio Soldano created WFLY-4919:
-------------------------------------

             Summary: Jandex backward compatibility issue
                 Key: WFLY-4919
                 URL: https://issues.jboss.org/browse/WFLY-4919
             Project: WildFly
          Issue Type: Bug
            Reporter: Alessio Soldano
            Assignee: Jason Greene


Starting few days ago, I'm seeing a regression in JBossWS testsuite caused by the latest upgrade of Jandex in WFLY.
The exception on server log says:
{noformat}
2015-07-14 00:28:09,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jaxws-samples-wsse-policy-trust-sts-holderofkey.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsse-policy-trust-sts-holderofkey.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-samples-wsse-policy-trust-sts-holderofkey.war"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component TestSecurityTokenService
        at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:96)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
        ... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0058: No matching field found for 'ObjectType'
        at org.jboss.as.ee.component.FieldInjectionTarget.getField(FieldInjectionTarget.java:82)
        at org.jboss.as.ee.component.FieldInjectionTarget.isStatic(FieldInjectionTarget.java:61)
        at org.jboss.as.ee.component.AbstractComponentConfigurator.mergeInjectionsForClass(AbstractComponentConfigurator.java:80)
        at org.jboss.as.ee.component.DefaultComponentConfigurator$1.handle(DefaultComponentConfigurator.java:78)
        at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54)
        at org.jboss.as.ee.component.DefaultComponentConfigurator.configure(DefaultComponentConfigurator.java:80)
        at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:82)
        ... 6 more
{noformat}
JBossWS install scripts overwrites some libraries in WildFly modules, including Apache CXF jars. In particular, the cxf-rt-ws-security-jandex jar is replaced with one generated by the jbossws build, which currently relies on Jandex 1.0.3.Final (but I've tried with 1.1.0.Final too, same issue).

I tried moving to the same Jandex version that's in WildFly (2.0.0.Beta3) and replacing the cxf-rt-ws-security-jandex jar only and that solves the problem.

Now, I can likely modify the jbossws build to use different jandex versions depending on the target container, but I wonder if this is some kind of backward compatiblity issue that needs to be dealt with more in general on the WildFly side.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)