Hide Forgot
Starting the current ER7 test results in the following error being displayed. 10:26:55,501 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bpel-console]] (ServerService Thread Pool -- 60) JBWEB000289: Servlet ErraiServlet threw load() exception: java.lang.NoSuchMethodError: com.google.common.collect.ImmutableSet.of([Ljava/lang/Object;)Lcom/google/common/collect/ImmutableSet; at org.reflections.util.ConfigurationBuilder.setScanners(ConfigurationBuilder.java:62) [reflections-0.9.5-RC2_jboss-SP1.jar:] at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.<init>(MetaDataScanner.java:64) [errai-bus-1.1-Final.jar:1.1-Final] This occurs because the war file is retrieving this from the system/layers/base/com/google/guava module rather than using the one embedded in the war file. The only way we have discovered to address this issue has been to export all of the war's jar/classes via a new module and have the war file depend on this module, thereby bypassing the additional dependencies that are being added to the classpath. The following steps were taken to address this - move the contents of switchyard-bpel-console.war/WEB-INF/lib to a new module (org.switchyard.bpel-console-lib), removing the original directory - jar the switchyard-bpel-console.war/WEB-INF/classes and place them in the new module (switchyard-bpel-console.jar), removing the original directory - alter the META-INF/jboss-deployment-structure.xml to have a dependency on the new module. I'll attach the module and jboss-deployment-structure.xml to this issue
Created attachment 832824 [details] The new module structure/contents
Created attachment 832825 [details] The jboss-depoyment-structure.xml for the switchyard-bpel-console.war
X:ref: Bug 1036559 Fixed by 7ca9ef841a41bbe43e3467d9053b490e881a00b2
Updated with commit 78edf681677082941e4db87ce760a6cac3c2a2b0 in ip: Back out 7ca9ef841a41bbe43e3467d9053b490e881a00b2: BZ1036559 / BZ1038267 Fix for BPMConsole GoogleCollections/Guava clash The real bug is in the Drools/jBPM modules, so we'll fix it there instead. The correct jboss-deployment-structure.xml files are included in RiftSaw 3.0.0.Final-ip6.0-ER7-3 (and removed from BPM Console in 2.4.5.Final-ip6.0-ER7-2).
It looks like the fixes are not in ER8: pwd /jboss/local/SOA_servers/SOA6/ER8/install Dir space/jboss-eap-6.1/standalone/deployments/switchyard-bpel-console.war/WEB-INF ll total 24 drwxrwxr-x. 3 ldimaggi ldimaggi 4096 Jan 6 13:56 classes -rw-rw-r--. 1 ldimaggi ldimaggi 1433 Dec 19 05:10 jboss-deployment-structure.xml -rw-rw-r--. 1 ldimaggi ldimaggi 416 Dec 19 04:54 jboss-web.xml drwxrwxr-x. 2 ldimaggi ldimaggi 4096 Jan 6 13:56 lib -rw-rw-r--. 1 ldimaggi ldimaggi 768 Dec 19 04:49 picketlink.xml -rw-rw-r--. 1 ldimaggi ldimaggi 2889 Dec 19 04:54 web.xml grep org.switchyard.bpel-console-lib * (no matches)
The original fix, proposed in the description, has now been reverted and is no longer needed. The underlying cause of this issue was the BRMS/BPMS modularisation, which is no longer included in the FSW distribution as we have reverted to the SY versions of their modules.
Verified in CR1