We do not want to define a specific mechanism for implementing the remote invocation mechanism used with the workflow API. Yet it is obvious that any implementation can profit from the possibility to execute several actions as one call to the server.
@param batch the batch to be executed.
@return the result returned by {@link Batch#execute Batch.execute
}.
@throws RemoteException if a system-level error occurs.
@throws InvocationTargetException if thrown by {@link Batch#execute Batch.execute
}
If one of the commands in the batch fails, this method can throw a BatchUpdateException and the JDBC driver may or may not process the remaining commands. The JDBC driver must behave consistently with the underlying database, either always continuing or never continuing. If the driver continues processing, the array of results returned contains the same number of elements as there are commands in the batch, with a minimum of one of the elements having the EXECUTE_FAILED value. @return an array of update counts, with one entry for each command in thebatch. The elements are ordered according to the order in which the commands were added to the batch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|