oracle.jdeveloper.offlinedb.handler
Class DeleteHandler

java.lang.Object
  oracle.jdeveloper.offlinedb.handler.DeleteHandler

public class DeleteHandler
extends java.lang.Object

Handles the logic for deleting offline db schemas and inter-dependent schema objects. It can inspect dependencies between the objects in a project, and determine whether or not objects can be deleted. The user is presented with appropriate dialogs before the operation is performed.

Constructor Summary

DeleteHandler()

Method Summary

void	handleDelete(java.util.Collection<? extends Element> elems, OfflineDBObjectProvider pro, boolean confirm)
void	handleDelete(Context c, OfflineDBObjectProvider pro)
void	handleDelete(SystemObject[] objs, OfflineDBObjectProvider pro) Handles the delete of the given schema objects from their provider.
void	handleDelete(SystemObject[] objs, OfflineDBObjectProvider pro, boolean confirm) Deprecated. - confirm is automatically controlled by the offline database.
void	handleDeleteProvider(Context c) Deletes a schema, or number of schemas if more than one is selected.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

DeleteHandler

public DeleteHandler()

Method Detail

handleDelete

public void handleDelete(Context c,
                         OfflineDBObjectProvider pro)
                  throws DBException

Throws:

DBException

handleDelete

public void handleDelete(java.util.Collection<? extends Element> elems,
                         OfflineDBObjectProvider pro,
                         boolean confirm)
                  throws DBException

Throws:

DBException

handleDelete

public void handleDelete(SystemObject[] objs,
                         OfflineDBObjectProvider pro)
                  throws DBException

Handles the delete of the given schema objects from their provider. The objects are analyzed for FK dependecies and if there are any unresolved from the list of objects to delete then those that are depended upon will not be deleted and the user alerted. Confirmation dialogs for the delete are displayed before the objects are actually removed.

Parameters:

objs -

pro -

Throws:

DBException - - If there is an error. Note that a HandlerFailedException is thrown if the error has been dealt with (i.e. an error displayed to the user) and nothing deleted.

handleDelete

@Deprecated
public void handleDelete(SystemObject[] objs,
                                    OfflineDBObjectProvider pro,
                                    boolean confirm)
                  throws DBException

Deprecated. - confirm is automatically controlled by the offline database.

Throws:

DBException

handleDeleteProvider

public void handleDeleteProvider(Context c)
                          throws DBException

Deletes a schema, or number of schemas if more than one is selected. The selected item in the given Context must be a SchemaFolder, or AppNavSchemaFolder if only one element is selected.

Throws:

DBException