Bug 1236100 - Message Console does not get shown in the AuthoringPerspectiveNoContext perspective
Summary: Message Console does not get shown in the AuthoringPerspectiveNoContext persp...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR1
: 6.2.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
: 1235736 (view as bug list)
Depends On:
Blocks: 1236104
TreeView+ depends on / blocked
 
Reported: 2015-06-26 14:27 UTC by Anton Giertli
Modified: 2020-03-27 19:45 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 1236104 (view as bug list)
Environment:
Last Closed: 2020-03-27 19:45:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Anton Giertli 2015-06-26 14:27:36 UTC 
Description of problem:
AuthoringPerspectiveNoContext perspective does not include Message section

Most likely because it is not on the whitelist
https://github.com/droolsjbpm/kie-wb-common/blob/6.2.x/kie-wb-common-services/kie-wb-common-services-api/src/main/java/org/kie/workbench/common/services/shared/messageconsole/MessageConsoleWhiteListImpl.java

Version-Release number of selected component (if applicable):
bpm 6.1.0

How reproducible:

always
Steps to Reproduce:
1.
2.
3.

Actual results:

AuthoringPerspectiveNoContext  perspective does not include Message section
Expected results:
AuthoringPerspectiveNoContext does  include Message section


Additional info:
Comment 1 Anton Giertli 2015-06-26 14:28:43 UTC 
This is the perspective in question
https://github.com/droolsjbpm/kie-wb-distributions/blob/6.2.x/kie-drools-wb/kie-drools-wb-webapp/src/main/java/org/kie/workbench/drools/client/perspectives/DroolsAuthoringNoContextNavigationPerspective.java
Comment 4 Anton Giertli 2015-06-26 14:35:11 UTC 
*** Bug 1235736 has been marked as a duplicate of this bug. ***
Comment 8 Zuzana Krejčová 2015-09-17 09:21:43 UTC 
Verified wit 6.2 ER2.
Note You need to log in before you can comment on or make changes to this bug.