Red Hat Bugzilla – Bug 1280345
[ENG](6.1.z) JAXB initialisation error - Several pairs of classes have the same XML type
Last modified: 2016-10-14 10:18:41 EDT
+++ This bug was initially created as a clone of Bug #1267906 +++
Description of problem:
The kie remote rest and jms rest is not working from switchyard components.
The switchyard components use the kie-remote-client to make this functionality working.
From Drools 6.2.0 this functionality is not working because the kie-remote-client. The reason is because this artifact can not be in the same classpath than the drools artifacts.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
git clone -c http.sslverify=false https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-soa/jbossqe-fsw-it.git
git checkout JBQA-9702_create-remote-bpms-api-test
mvn clean install -Pjboss-eap,bxms -pl :remote-bpms-api-test -am -Ddisable.groovy.compiler=true -Dversion.bom.fuse=6.2.1.redhat-020 -Dversion.switchyard=2.0.1.redhat-621020 -Dversion.fuse.integration=1.1.0.redhat-020
--- Additional comment from JBoss Product and Program Management on 2015-10-01 07:20:08 EDT ---
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from Alessandro Lazarotti on 2015-10-01 10:15:44 EDT ---
David see that Drools 6.2 (BRMS 6.1) does not support Remote API. It only targets
runtime engine executions.
For Drools 6.3 (BRMS 6.2) we expect to have the features for kie-remote-clients properly available in drools-karaf-features.xml and jars being properly "OSGFied":
The related BZ for this enhancement is :
Is not Fuse 6.2.1 supposed to be tested with BxMS 6.2 instead of 6.1 ? Why the tests are using Drools 6.2 instead of 6.3 ? Or this is a confusion about what mean Drools 6.2 versus BxMS 6.2 ?
I set this BZ as a blocker for BxMS 6.2.
--- Additional comment from David Virgil on 2015-10-01 10:49:57 EDT ---
The tests done by the qe have been with the previous fuse ER. The previous Fuse 6.2.1 ER tests were using our 1.1.x Fuse Integration Branch that was compatible with the 6.2.x Drools branch.
The tests done by the qe, are included here:
The tests are done using EAP 6.4
This error is happening in version 6.2.x and 6.3.x of drools.
--- Additional comment from Alessandro Lazarotti on 2015-10-01 10:50:54 EDT ---
what I said above is true for Fuse deployment, but by the mvn cmd it seems that you are testing in EAP. If it is the case, so we need to look a fix even for BxMS 6.1
--- Additional comment from JBoss Product and Program Management on 2015-10-01 14:02:36 EDT ---
This bug report previously had all acks and release flag approved.
However since at least one of its acks has been changed, the
release flag has been reset to ? by the bugbot (pm-jboss). The
ack needs to become approved before the release flag can become
--- Additional comment from Marco Rietveld on 2015-10-26 09:19:08 EDT ---
Work on this BZ has been tabled pending the outcome of a discussion among the BxMS and Fuse PM's and other involved parties.
--- Additional comment from Marco Rietveld on 2015-11-05 14:01:15 EST ---
--- Additional comment from Edson Tirelli on 2015-11-05 14:59:30 EST ---
Fixed. This is fuse-specific problem for community 6.2.x/product 6.1.x, and not related to the drools/jbpm code.
Verification of this bug requires integration package build.
In the link above you can find the last release.
The verification of this bug is currently blocked by this issue .
Commits with fix are missing in BxMS 6.1.5.CR2 tag. They are on master and 6.3.x branches only.
*No* commits in the BxMS code are required to fix this issue!
The short story is as follows: the Fuse integration code "hacked" (deeply) internal classes in the kie-remote-client, and when those internal classes changed, the Fuse integration code broke. The fix is simply to remove these hacks.
The commit that does this can be found here:
The longer story is that, because of some confusion, I ended up changing BxMS code in order to support functionality that the Fuse integration code was using: however, this "functionality" was 1. _never_ supported and 2. it's questionable if that functionality ever worked in the first place. In an ideal world, I would have reverted all of the commits above, but because of time pressures and other factors, they've been left in.
I hope this helps.
Thank you for help, but I did not find this commit  in "intpkg-1.0.0.redhat-620150" tag. This commit is present only in branches 1.2.x and 1.3.x of fuse-bxms-integ. This bugzilla is for BxMS 6.1.5 which corresponds to branches 1.0.x and 1.1.x. The fix seems to be not present here .
Hi JIri, THe commit is on 1.1.x:
yes commit is pressent on the branch 1.1.x. Unfortunately it is not cherry picked on branch 1.0.x and the current integration pack was build using brach 1.0.x. Here is the link on integration package  for BxMS 6.1.5.CR2.
Yes, I believe that Michael's create the tags from 1.0.x branch which is combination for Fuse 6.2.0+BRMS 6.1.5.
I also can't see the commit in 1.0.x branch though it present in 1.1.x, 1.2.x and 1.3.x.
We will release today the Patch Update 6.2.1.
The bug is not a blocker and can be delivered for 6.2.2, so no rebuild is necessary.
> We will release today the Patch Update 6.2.1.
I mean, 6.1.5
My bad, since it is the last patch update for BxMS 6.1.5 and Fuse 6.2.0, and it is already fixed for BxMS 6.2.0 + Fuse 6.2.1 (Bug 1267906) - then this is the last chance to have it in the first combination mentioned before.
Let's rebuild to get it in still for Integration Pack B6.1.5 x F6.2.0 release.
During the PM call, it was decided that a new tag will be created from branch 1.1.x, that already includes the fix.
Setting this ticket to MODIFIED.
(In reply to Edson Tirelli from comment #16)
> During the PM call, it was decided that a new tag will be created from
> branch 1.1.x, that already includes the fix.
> Setting this ticket to MODIFIED.
OK. Does it mean that we should use the combination build from 1.1.x to replace the one for 1.0.x?
@Michael, could you please prepare the tag based on 1.1.x branch?
Look at https://github.com/jboss-integration/fuse-bxms-integ/tree/fuse-bxms-integ-1.1.0.redhat-025
Verified with Integration package build "1.1.0.redhat-027" and BxMS 6.1.5.