Delete Role API

edit

Delete Role Request

edit

A DeleteRoleRequest has a single argument

DeleteRoleRequest deleteRoleRequest = new DeleteRoleRequest(
    "testrole");    

role to delete

Synchronous Execution

edit

When executing a DeleteRoleRequest in the following manner, the client waits for the DeleteRoleResponse to be returned before continuing with code execution:

DeleteRoleResponse deleteRoleResponse = client.security().deleteRole(deleteRoleRequest, RequestOptions.DEFAULT);

Asynchronous Execution

edit

Executing a DeleteRoleRequest can also be done in an asynchronous fashion so that the client can return directly. Users need to specify how the response or potential failures will be handled by passing the request and a listener to the asynchronous delete-role method:

client.security().deleteRoleAsync(deleteRoleRequest, RequestOptions.DEFAULT, listener); 

The DeleteRoleRequest to execute and the ActionListener to use when the execution completes

The asynchronous method does not block and returns immediately. Once it is completed the ActionListener is called back using the onResponse method if the execution successfully completed or using the onFailure method if it failed.

A typical listener for delete-role looks like:

listener = new ActionListener<DeleteRoleResponse>() {
    @Override
    public void onResponse(DeleteRoleResponse deleteRoleResponse) {
        
    }

    @Override
    public void onFailure(Exception e) {
        
    }
};

Called when the execution is successfully completed.

Called when the whole DeleteRoleRequest fails.

Delete Response

edit

The returned DeleteRoleResponse allows to retrieve information about the executed operation as follows:

boolean found = deleteRoleResponse.isFound();    

whether the given role was found