Persistent component support

The following are known issues with support for container-managed persistence in EJB entity beans.

Nonmapped tables

When using the “nonmapped tables” option for automatic persistence of entity components, automatic table creation works only for Sybase Adaptive Server Anywhere and Sybase Adaptive Server Enterprise database types.

EJB QL limitations

EAServer provides full support for EJB query language (EJB QL) in EJB 2.0 CMP entity beans, except for queries that take a parameter of type object reference.

CMP beans cannot display some Asian language strings

[CR #289457] If the server’s character set property is set to iso_1, CMP entity beans cannot retrieve Asian language strings that use another character set. Data is converted to iso_1 and nonmappable characters are lost.

Workaround: Change the server’s codeset to UTF-8 or an Asian character set that matches the data. To change the server’s codeset in Jaguar Manager, display the Server Properties dialog box and set the Codeset property on the General tab.

Prepared statement use with Adaptive Server Anywhere

When using Adaptive Server Anywhere with a CMP entity bean, you may see this error message:

ASA Error -685: Resource governor for prepared statements exceeded

Workaround: Edit the database type properties file in the EAServer Repository/DatabaseType subdirectory. Look for a line that contains “statementCache” and edit the setting to look like the following:

com.sybase.jaguar.databasetype.statementCache=false

If the statementCache setting is not present, add the line above to the file.

Copyright © 2005. Sybase Inc. All rights reserved.

View this release bulletin as PDF