1 /*******************************************************************************
\r
2 * Copyright (c) 2007, 2010 Association for Decentralized Information Management
\r
3 * in Industry THTH ry.
\r
4 * All rights reserved. This program and the accompanying materials
\r
5 * are made available under the terms of the Eclipse Public License v1.0
\r
6 * which accompanies this distribution, and is available at
\r
7 * http://www.eclipse.org/legal/epl-v10.html
\r
10 * VTT Technical Research Centre of Finland - initial API and implementation
\r
11 *******************************************************************************/
\r
12 package org.simantics.db.request;
\r
14 import org.simantics.db.AsyncReadGraph;
\r
15 import org.simantics.db.Session;
\r
16 import org.simantics.db.exception.CancelTransactionException;
\r
17 import org.simantics.db.procedure.AsyncProcedure;
\r
20 * TODO: fix this documentation, it is completely out-of-date!
\r
22 * The <code>GraphRequest</code> interface is used to create transaction
\r
23 * requests to Simantics database implementations. Both read and write
\r
24 * transaction requests use the same interface.
\r
27 * The actual work carried out by the implemented request should be done in the
\r
28 * <code>perform</code> method. It receives a <code>Graph</code> instance as
\r
29 * the only argument which is the interface for actually reading and writing the
\r
33 * Transaction requests can be made to the database by creating your own
\r
34 * <code>GraphRequest</code> instance and putting it in the request queue of
\r
35 * the database session through the {@link Session} interface. The database
\r
36 * session is responsible for executing the queued requests in a thread of its
\r
37 * choice, or possibly/preferably multiple threads. The database session can
\r
38 * allow multiple read-only requests to occur simultaneously, but read-write
\r
39 * requests require exclusive database access. In other words only one
\r
40 * read-write request can be in execution simultaneously.
\r
43 * This interface also has two callbacks - <code>handleException</code> for
\r
44 * allowing handling any exceptions thrown by <code>perform</code> and
\r
45 * <code>requestCompleted</code> for performing actions after a request has
\r
46 * been successfully completed.
\r
48 * @author Antti Villberg
\r
49 * @see AsyncReadGraph
\r
50 * @see AsyncProcedure
\r
53 public interface AsyncRead<Result> extends Request {
\r
56 * When a <code>GraphRequest</code> is serviced by the database session
\r
57 * the method <code>perform</code> is invoked.
\r
60 * Perform receives an object instance implementing the <code>Graph</code>
\r
61 * interface which provides the only way to read/write the graph data model.
\r
62 * The Graph instance must only be valid during the execution of the
\r
63 * <code>perform</code> method and therefore should not be stored for use
\r
64 * outside of its execution.
\r
67 * The general contract of the method <code>perform</code> is that it may
\r
68 * take any action whatsoever which involves reading or writing the data
\r
69 * model through the received Graph instance.
\r
71 * @param g an interface for reading and writing the data model
\r
72 * @return the result status of the request which affects how the
\r
73 * transaction proceeds, see GraphRequestStatus for more information
\r
74 * @throws Exception when anything goes wrong inside the request thread
\r
75 * @throws CancelTransactionException to indicate that the request needs to
\r
76 * be cancelled and any changes rolled back
\r
78 void perform(AsyncReadGraph graph, AsyncProcedure<Result> procedure);
\r