Created attachment 831628 [details] screenshot Description of problem: Creating a new GDT ends with a white screen. No error message, no stacktrace appears in a server log. This GDT cannot be opened. However, after clicking on packages under the opened project in Project Explorer, GDT can now be opened and new one created without any problem. I have used a clear example repository to reproduce this issue. tested with: BRMS-6.0.0.ER5
Can you provide the exact steps you followed to create the decision table? I did the following and it worked OK:- 1) New project 2) New Guided Decision Table (path was src/main/resources) 3) Decision Table editor opened showing empty decision table 4) Project Explorer showed new guided decision table.
(In reply to manstis from comment #1) > Can you provide the exact steps you followed to create the decision table? > > I did the following and it worked OK:- > > 1) New project > 2) New Guided Decision Table (path was src/main/resources) > 3) Decision Table editor opened showing empty decision table > 4) Project Explorer showed new guided decision table. Hi Michael, we probably differ in step 1), because I used example repository - which does not contain any assets, but empty project is already here. I think this is a matter of somehow not fully initialized Project Explorer. Some actions - like creating a new project, or navigating in it's packages make it work properly, but without these actions GDT cannot be opened.
Can you provide the example repository? Have you tried creating a new project and replicating this issue? What did you want to do with this BZ?
(In reply to manstis from comment #3) > Can you provide the example repository? It's the example repository that is available in business-central by setting system property org.kie.example=true before starting EAP. > Have you tried creating a new project and replicating this issue? Yes, I have just tried these steps: 1. create new repository 2. create new project 3. create new GDT Again, I got a white screen instead of GDT editor 4. close the GDT editor window, reopen GDT => white screen 5. repeat ^ => GDT opened successfuly > What did you want to do with this BZ? As it seems, this issue occurs only for the first time - when I make it work by navigating in the project packages or by steps described above, I am unable to reproduce it even after restarting EAP. Only erasing niogit enables me to see this issue again. On the other hand, this behaviour is very confusing. Make your own opinion, I am attaching a video with those reproducing steps.
Created attachment 832477 [details] video with reproducing steps
Thanks for the detaisl and video. This helped me understand the issue a lot. Can you please advise where BRMS-6.0.0.ER5 can be downloaded from as I cannot replicate with the community version. Thanks.
(In reply to manstis from comment #6) I'm glad it helped. Here is a link to ER5 binaries: http://dev138.mw.lab.eng.bos.redhat.com/candidate/brms-6.0.0-ER5/ and jboss-brms-6.0.0-redhat-5-deployable-eap6.x.zip is what you want. Just unzip and copy into EAP 6.1.1 installation.
Pedro, I hope you don't mind me assigning this to you for the missing EAP-INTEGRATION commits to be investigated. The current ER5 build for EAP doesn't "behave" correctly... events appear to be lost - the description of this BZ gives one example; others I've seen trying ER5 on EAP6.1.1 include Project Explorer not updating and files not being opened. This behavior is not evident in the community FINAL release. Since only operation on EAP is problematic I can only, at this time, assume there is a problem with the EAP packaging.
Reclaimed! Built jboss-integration (https://github.com/organizations/jboss-integration) at sync.2013.11.19 tag (i.e. ER5) locally. I repeated the steps in this BZ and it worked OK without problem. Given the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1038175, it could be possible that ER5 has been built incorrectly; causing this problem. I've contacted Ryan Zhang to check if ER5 was indeed built with correct dependencies.
See the "See Also" BZ. Performing the same operation (i.e. clearing my browser cache) this problem disappeared with BRMS ER5 on EAP6.1.1.
We're still unconvinced this is completely fixed. Assigning back to me until we've tested on jboss-integration.11.19 on AS7 and EAP.
Both jboss-as7.0.war and eap-6_1.war work without any sign of this issue (build from kie-wb-distributions, sync.2013.11.19)
Tested with kie-drools-wb-6.0.0-SNAPSHOT-jboss-as7.0.war built from jboss-integration.11.19 and this worked OK... trying distribution for EAP now...
Tested with eap-modules-distributions-6.0.0-SNAPSHOT-org.kie.kie-drools-wb-webapp.war built from jboss-integration.11.19 on EAP6.2 and this worked OK too... trying on EAP6.1.1.
Tested with eap-modules-distributions-6.0.0-SNAPSHOT-org.kie.kie-drools-wb-webapp.war built from jboss-integration.11.19 on EAP6.1.1 and this worked OK too... I suggest there is little we can do other than re-test on the next ER release?
I should add I've tested on both FF12.0 and Chrome 31.
Just to be clear on what Michael said, the tag sync.2013.11.19 (ER5), built with the source maven build, does not seem to have the problem, while the same tag, built with the product build script has the problem. Our best guess is that there is a difference between the 2 build scripts (like an overridden or clashing dependency). Our suggestions is for the productization team to double check the product build looking for it, or we risk the problem happening again in ER6.
Raising severity because this seems to be a deeper issue (see comments above).
The observed issue still persists (BRMS-6.0.0.ER7). Many operations are faster in comparison with the video I attached before, but Guided Decision Table can be opened only on the 3rd attempt.
As discussed during the triage call, this ticket will be postponed to 6.0.1.
Required release note for 6.0.0
I checked with the build for CR2 and could not reproduce; using system properties -Dorg.kie.example=true -Dorg.kie.demo=false. Please check and advise if you are able to reproduce with later build.
This no longer has a target release of 6.0.0.
Verified with BRMS-6.0.1.ER1