Red Hat Bugzilla – Bug 1255821
Expose deleteBundleDestination for BundleManagerRemote in JBoss ON CLI
Last modified: 2015-11-01 19:45:00 EST
Description of problem:
Currently BundleManagerRemote does not have any method available to delete the specific bundle destination using JON CLI. But the JON GUI has functionality to delete specific bundle destination, JON CLI should provide method e.g. deleteBundleDestination to delete the specific bundle destination based on bundle destination id.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
time: 2015-09-02 10:58:00 +0200
author: Libor Zoubek - firstname.lastname@example.org
message: Bug 1255821 - Expose deleteBundleDestination for BundleManagerRemote in
JBoss ON CLI
Method moved from BundleManagerLocal to BundleManagerRemote,
changed javadocs a bit (description taken from UI confirmation
Cherry-picked to release/jon3.3.x:
Author: Libor Zoubek <email@example.com>
Date: Wed Sep 2 10:58:00 2015 +0200
Bug 1255821 - Expose deleteBundleDestination for BundleManagerRemote in
JBoss ON CLI
Method moved from BundleManagerLocal to BundleManagerRemote, changed
javadocs a bit (description taken from UI confirmation message)
(cherry picked from commit d9960319df7ed1824b5a61baefe15359a4e3b333)
Moving to ON_QA as available to test with the following build:
*Note: jon-server-patch-3.3.0.GA.zip maps to ER01 build of
3.3.0.GA Update 04
Build Number :
BundleManager.deleteBundleDestination(int) is working correctly. Automation updated to cover this method as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.