web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Container-managed data access support By default, the Borland CMP engine does not automatically map cmp-field to LOBs. If you intend to use LOB data types, you must inform the CMP engine explicitely in the ejb-borland.xml deployment descriptor. You do this by setting the Column Property createColumnSql. For example: CLOB-column createColumnSql String> CLOB BLOB-column createColumnSql String> BLOB Container-created tables You can instruct the Borland EJB Container to automatically create tables for container-managed entities based on the entity's container-managed fields by enabling the create-tables property. Because table creation and data type mappings vary among vendors, you must specify the JDBC database dialect in the deployment descriptor to the Container. For all databases (except for JDataStore) if you specify the dialect, then the Container automatically creates tables for container-managed entities for you if the create-tables property is set to true. The Container will not create these tables unless you specify the dialect. The following table shows the names or values for the different dialects (case is ignored for these values): Database Name JDataStore Oracle Sybase MSSQLServer DB2 Interbase Informix Dialect Value jdatastore oracle sybase mssqlserver db2 interbase informix Chapter 17: EJB-QL and Data Access Support 161
162 BES Developer’s Guide
- Page 121 and 122: 110 BES Developer’s Guide
- Page 123 and 124: Container-managed persistence and R
- Page 125 and 126: Implementing an entity bean Generat
- Page 127 and 128: Container-Managed Persistence in Bo
- Page 129 and 130: Container-Managed Persistence in Bo
- Page 131 and 132: Setting Properties Setting Properti
- Page 133 and 134: Setting Properties into a BLOB. The
- Page 135 and 136: Setting Properties Automatic table
- Page 137 and 138: 126 BES Developer’s Guide
- Page 139 and 140: Container-managed persistence and R
- Page 141 and 142: Container-Managed Persistence in Bo
- Page 143 and 144: Container-Managed Persistence in Bo
- Page 145 and 146: Container-Managed Persistence in Bo
- Page 147 and 148: Container-Managed Persistence in Bo
- Page 149 and 150: Container-Managed Persistence in Bo
- Page 151 and 152: Container-Managed Persistence in Bo
- Page 153 and 154: 142 BES Developer’s Guide
- Page 155 and 156: Setting Properties J2EE 1.3 Entity
- Page 157 and 158: Setting Properties Figure 16.2 Edit
- Page 159 and 160: Setting Properties Table 16.1 ejb.m
- Page 161 and 162: Setting Properties Table 16.3 Table
- Page 163 and 164: Setting Properties Security Propert
- Page 165 and 166: Aggregate Functions in EJB-QL Selec
- Page 167 and 168: Support for ORDER BY Support for OR
- Page 169 and 170: Overriding SQL generated from EJB-Q
- Page 171: Container-managed data access suppo
- Page 175 and 176: Generating primary keys from a cust
- Page 177 and 178: Implementing primary key generation
- Page 179 and 180: Transaction manager services Consis
- Page 181 and 182: Transaction manager services When t
- Page 183 and 184: Transaction manager services Follow
- Page 185 and 186: Declarative transaction management
- Page 187 and 188: Declarative transaction management
- Page 189 and 190: JDBC API Modifications JDBC API Mod
- Page 191 and 192: Handling of EJB exceptions Applicat
- Page 193 and 194: 182 BES Developer’s Guide
- Page 195 and 196: Client View of an MDB Client View o
- Page 197 and 198: Clustering of MDBs This is yet anot
- Page 199 and 200: Error Recovery Redelivered messages
- Page 201 and 202: 190 BES Developer’s Guide
- Page 203 and 204: JNDI Definitions Module Important s
- Page 205 and 206: Disabling and Enabling a Deployed D
- Page 207 and 208: Configuring JDBC Datasources In the
- Page 209 and 210: Configuring JDBC Datasources To add
- Page 211 and 212: Defining the Connection Pool Proper
- Page 213 and 214: Defining the Connection Pool Proper
- Page 215 and 216: Descriptions of Borland Enterprise
- Page 217 and 218: Advanced Topics for Defining JDBC D
- Page 219 and 220: Connecting to JDBC Resources from J
- Page 221 and 222: Configuring JMS Connection Factorie
Container-managed data access support<br />
By default, the <strong>Borland</strong> CMP engine does not automatically map cmp-field to LOBs. If<br />
you intend to use LOB data types, you must inform the CMP engine explicitely in the<br />
ejb-borland.xml deployment descriptor. You do this by setting the Column Property<br />
createColumnSql. For example:<br />
<br />
CLOB-column<br />
<br />
createColumnSql<br />
String><br />
CLOB<br />
<br />
<br />
<br />
BLOB-column<br />
<br />
createColumnSql<br />
String><br />
BLOB<br />
<br />
<br />
Container-created tables<br />
You can instruct the <strong>Borland</strong> EJB Container to automatically create tables for<br />
container-managed entities based on the entity's container-managed fields by enabling<br />
the create-tables property. Because table creation and data type mappings vary<br />
among vendors, you must specify the JDBC database dialect in the deployment<br />
descriptor to the Container. For all databases (except for JDataStore) if you specify the<br />
dialect, then the Container automatically creates tables for container-managed entities<br />
for you if the create-tables property is set to true. The Container will not create these<br />
tables unless you specify the dialect.<br />
The following table shows the names or values for the different dialects (case is<br />
ignored for these values):<br />
Database Name<br />
JDataStore<br />
Oracle<br />
Sybase<br />
MSSQLServer<br />
DB2<br />
Interbase<br />
Informix<br />
Dialect Value<br />
jdatastore<br />
oracle<br />
sybase<br />
mssql<strong>server</strong><br />
db2<br />
interbase<br />
informix<br />
Chapter 17: EJB-QL and Data Access Support 161