Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1059319 - kie-config-cli asks for KBase and KSession in remove-deployment command
Summary: kie-config-cli asks for KBase and KSession in remove-deployment command
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Maciej Swiderski
QA Contact: Radovan Synek
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-29 16:09 UTC by Radovan Synek
Modified: 2014-01-29 16:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-01-29 16:58:47 UTC
Type: Bug

Attachments (Terms of Use)

Description Radovan Synek 2014-01-29 16:09:24 UTC
To identify an deployment unit, only groupId, artifactId, version are sufficient. KBase and KSession are unnecessary information for remove-deployment operation and user should not be asked for them.

Comment 1 Maciej Swiderski 2014-01-29 16:50:28 UTC
Radek, actually they are used. When you deploy kjar that has multiple kbase/ksession definitions they will be deployed as separate deployments and will run in parallel on runtime environment. So that's why when adding and removing deployments users are asked to provide kbase and ksession name.

While this is in most cases an optional you might simply leave it empty and move on, but in some cases it will be actually required to undeploy the right deployment.

Does that make sense?

Comment 2 Radovan Synek 2014-01-29 16:58:47 UTC
Maciej, of course it makes sense, thanks for clarification.

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