Bug 1273898 - JON CLI deleteEventsForContext has signature which does not match remote usage.
Summary: JON CLI deleteEventsForContext has signature which does not match remote usage.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: CLI
Version: JON 3.3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 3.3.6
Assignee: Michael Burman
QA Contact: Mike Foley
URL:
Whiteboard:
: 1273900 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-21 13:22 UTC by Prachi
Modified: 2016-06-02 15:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-02 15:15:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Prachi 2015-10-21 13:22:15 UTC
Description of problem:

JON CLI "deleteEventsForContext" has signature which does not match  remote usage.

it accepts EntytiContext and List<Integer> ids. This signature is not consistent with the rest of remote APIs.

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


How reproducible:


Steps to Reproduce:

var criteria=EntityCriteria();
EventManager.findEventsByCriteria(criteria);
event= EventManager.findEventsByCriteria(criteria);
var eventDetail=event.get(0);
eventDetail.id                                                                                    
15554

EventManager.deleteEventsForContext(EntityContext.forResource(10003),15554);(not working)
EventManager.deleteEventsForContext(EntityContext.forResource(10003),eventDetail.id); (not working)

Actual results:


Expected results:

It should delete the events

Additional info:

deleteEventsForContext has unfortunately signature which does not match (enough) remote usage.

it accepts EntytiContext and List<Integer> ids. This signature is not consistent with the rest of remote APIs.

We can test like this:

var list = java.util.ArrayList()
list.add(new java.lang.Integer(10054))

EventManager.deleteEventsForContext(EntityContext.forResource(10003), list)


However, this is not user friendly which would accept int... ids etc.

Comment 1 Filip Brychta 2015-10-22 14:44:03 UTC
*** Bug 1273900 has been marked as a duplicate of this bug. ***


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