Inc. Server User Manual

Additional Upgrade Procedures and Information
BEA WebLogic Server 7.0 Upgrade Guide 1-27
Fully Qualified Path Expressions
In an EJB QL Query on WebLogic Server 7.0, all path-expressions must be fully
qualified. This is a change from WebLogic Server 6.x. If you see an ejbc error while
running ejbc on WebLogic Server 7.0 using a 6.x EJB, you need to correct either your
ejb-ql elements in your ejb-jar.xml file or your weblogic-ql elements in your
weblogic-cmp-jar.xml file. For example:
 WebLogic Server 6.x would allow the following query to compile:
SELECT address FROM CustomerBean AS c WHERE zip = ?1
 For WebLogic Server 7.0 to allow the same query to be compiled, the address
and zip fields must be qualified:
SELECT c.address FROM CustomerBean AS c WHERE c.zip = ?1
jCOM
For information about upgrading from WebLogic jCOM 6.1 to WebLogic jCOM 7.0
see Upgrading Considerations in Programming WebLogic jCOM.
JDBC
The minimum capacity increment for a JDBC connection pool has changed from 0, in
WebLogic Server 6.1, to 1, in version 7.0. See JDBCConnectionPool in the WebLogic
Server Configuration Reference.
The default value for
PreparedStatementCacheSize and
XAPreparedStatementCacheSize in the JDBC Connection Pool MBean has
increased from 0 in WebLogic Server 6.1 to 5 in WebLogic Server 7.0SP2 and later
releases. For more information about the Prepared Statement Cache and its limitations,
see “Increasing Performance with the Prepared Statement Cache” in the
Administration Guide.