Справочник Пользователя для BEA 7

BEA WebLogic Server 7.0 Upgrade Guide

„

Based on the inclusion of support for JTA, the JTS JDBC driver (with properties 
in 

weblogic.jts.*

 and URL 

jdbc:weblogic:jts

:..) has been replaced by a 

JTA JDBC/XA driver. Existing properties are available for backward 
compatibility, but you should change the class name and properties to reflect the 
JTS to JTA name change.

The following changes have been made to JDBC:

„

The WebLogic T3 API was deprecated in WebLogic Server 6.1; use the RMI 
JDBC driver in its place. This also applies to users porting from WebLogic 
Server 4.5.x.

„

The

 weblogic.jdbc20.*

 packages are being replaced with 

weblogic.jdbc.*

 

packages. All WebLogic JDBC drivers are now compliant with JDBC 2.0.

„

If you have a current connection and are using a 

preparedStatement

, and the 

stored procedure gets dropped in the DBMS, use a new name to create the stored 
procedure. If you recreate the stored procedure with the same name, the 

preparedStatement

 will not know how to access the newly created stored 

procedure—it is essentially a different object with the same name. 

The behavior of the JSP include directive has changed between WebLogic Server 5.1 
and the current version. In versions through WebLogic Server 5.1, the JSP include 
directive logged a Warning-level message if it included a non-existent page. In 
WebLogic Server 6.0 and later, it reports 500 Internal Server Error in that case.You 
can avert the error by placing an empty file at the referenced location.