You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: