Skip to content

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

@rahul-rj

Description

@rahul-rj

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."));

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions