Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in wildlfy-core causing MessagingServices class loader failure #21

Open
rahul-rj opened this issue Sep 4, 2019 · 0 comments
Open

Comments

@rahul-rj
Copy link

rahul-rj commented Sep 4, 2019

As we have moved to ActiveMQ instead of HornetQ from wildfly 10 onwards, we need to update the logic in the ASUtils.java in wildfly-core to support the newer versions of wildfly. Due to the incorrect logic of getting the variable initialized depending on the wildfly version in the file https://github.com/projectodd/wunderboss/blob/master/wildfly/core/src/main/java/org/projectodd/wunderboss/as/ASUtils.java, deployment is failing to get the correct path for MessagingService module. Please revisit the logic to initialize the variable so that it can work for wildfly 10 onwards. Here is the faulty code, which is looking only for the wildfly 10 version to enable the path for activeMQ modules and failing for wildfly 11 onwards.

           CONTAINER_IS_WILDFLY_9 =
               type == ContainerType.WILDFLY && version.startsWith("9.");
           CONTAINER_IS_WILDFLY_10 =
               "JBoss EAP".equals(productName)
               ||
               (type == ContainerType.WILDFLY && version.startsWith("10."));
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant