|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface SqlDataSource
For prototyping purposes, the ISC server supports basic SQL connectivity for DataSources
defined in XML. Because the request processing flow for the built-in SQL engine is
identical to the flow used for
'integrating with other Java storage engines'
,
when your application grows past prototype stage you can switch to a different storage
engine without wasted work.
To use the built-in SQL engine, declare a DataSource
in XML format with
serverType
set to "sql", and place it in the shared dataSources directory
([webroot]/shared/ds by default) in a file called "[dataSourceId].ds.xml".
You can then use the 'Admin Console'
to configure database access,
as well as to automatically create and populate a database table based on your DataSource.
By default, DataSources will use the "default database" from the admin console, however you
can set dbName
to the name of a specific database configuration you have
configured via the Admin Console.
The list of databases known to work with the the built-in SQL logic is as follows:
HSQLDB 1.7.x, 1.8.x | ||
IBM DB2 8.x, 9.x | ||
MS SQL Server 2000 | ||
MySQL 3.2.x, 4.0.x, 4.1.x, 5.0.x, 5.1.x | ||
Oracle 8.0.5, 8i, 9i, 10g | ||
PostgreSQL 7.x, 8.x |
You will also need a JDBC driver for your specific database. Licensing restrictions prevent us including any JDBC driver other than the one for HSQLDB. However, you can download these drivers for free from the vendors' websites. If your specific database server or version is not listed above, please go to the SmartGWT forums for assistance.
You can also connect to an existing database table - the ISC SQL engine simply generates a
DB table whose columns match the DataSource field names and types, so you can instead
declare a DataSource whose fields match an existing table. To troubleshoot such an
integration, you can look at the generated SQL for both table creation and DSRequest
handling in the server-side log.
Once you have your SQL DataSource connected to a table, in a default SDK installation,
DSRequests for your DataSource will be sent to the default
com.smartgwt.client.rpc.RPCManager#actionURL
, and hence handled automatically, without you having
to write any Java code, by the com.smartgwt.client.docs.Xml
.
IDACall is a very simple servlet that just calls the server-side method
dsRequest.execute() for all inbound requests.
If you need to customize how DSRequests are handled on the server, you can write your own
version of the IDACall servlet to dispatch requests, as described under RPCManager
and exemplified by the
Custom DataSource Integration example.
This allows you add your own logic either before or after calling dsRequest.execute()
to invoke the normal behavior of the SQL engine. This means you can implement:
Relogin
)
DataSourceField.getSequenceName()
|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |