Bug 1263102 - Error modal shown when deleting data source.
Error modal shown when deleting data source.
Status: ASSIGNED
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: BAM (Show other bugs)
6.2.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: David Gutierrez
Jan Hrcek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-15 02:59 EDT by Jan Hrcek
Modified: 2016-02-19 08:41 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot illustrating the issue. (34.53 KB, image/png)
2015-09-15 02:59 EDT, Jan Hrcek
no flags Details

  None (edit)
Description Jan Hrcek 2015-09-15 02:59:23 EDT
Created attachment 1073503 [details]
Screenshot illustrating the issue.

Description of problem:
The following error modal is displayed after I delete any (my custom created or predefined) of the datasources in DataSet perspective (see screenshot):

Error
User root has deleted the following resource default://master@datasets/definitions/c805471b-d9ff-4cc2-8025-57dba21b02b7.dset.

This is quite confusing, because above this modal there's notification "Item successfully deleted" and the data set seems to be deleted successfully (not shown in data set explorer anymore).

Version-Release number of selected component (if applicable):
kie-wb: 6.3.x snapshot

How reproducible:
Always

Steps to Reproduce:
1. Navigate to DataSets perspective
2. Expand any data set in DS Explorer
3. Click edit button
4. In data set editor panel that opens, click Delete button at the top right.

Actual results:
Modal with error (see above) displayed.

Expected results:
If deletion is successful, no modal should be dispalyed (the notification is enough).
Comment 1 Jan Hrcek 2016-02-19 08:41:58 EST
Checking today's 6.4.x community snapshot the issue is still present.

Note You need to log in before you can comment on or make changes to this bug.