FSW: We have found an issue that is blocking our use of the current module structure, discovered when we went to package multiple Errai based consoles into the same server. The kie lib module contains the Errai reflections jar and, through that, we are seeing classes leak from one war context into the other. This is causing ClassCastExceptions to be raised. We are trying to find a workaround for this problem however it is beginning to look like we may need this to be fixed within the BRMS/BPMS modularisation. Probably it would be enough to move the errai reflections jar to the webapp, and remove it from the kie lib module.
Two errai artifacts have been removed from org.kie.lib module: org.jboss.errai.io.netty:netty:jar org.jboss.errai.reflections:reflections:jar This artifacts will be located in the webapp library as none module uses them. Commit on 6.0.X =============== https://github.com/droolsjbpm/kie-wb-distributions/commit/78f101e7ee563e3772d0863f1c74b92bdd75da88 Commit on master ================ https://github.com/droolsjbpm/kie-wb-distributions/commit/dc2e7c524bb7a5745f553231b36341b04b224d01
To be sure, I have verified the maven dependency tree for artifacts: (1) org.jboss.errai.io.netty:netty:jar (2) org.jboss.errai.reflections:reflections:jar Artifact (1) is used by org.jboss.errai:errai-bus:jar, and artifact (2) is used by org.guvnor:guvnor-workingset-api:jar, both artifacts are located in the webapp classloader, so moving those errai artifacts to webapp classloader will have no impact in modules behaviour.
This is rather internal productization issue, which was fixed in ER5, where EAP 6.1.1 modules are supported. Verified in ER5.