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

BEA WebLogic Server 7.0 Upgrade Guide

Due to a change in the JSP specification, null request attributes now return the string 
“null” instead of an empty string. WebLogic Server versions since 6.1 contain a new 
flag in 

weblogic.xml

 called 

printNulls

 which is true by default, meaning that 

"null" will be the default. Setting this to false ensures that expressions with "null" 
results are printed as an empty string, not the string “null.”

An example of configuring the 

printNulls

 element in 

weblogic.xml

 :

<weblogic-web-app>

   <jsp-param>

     <param-name>printNulls</param-name>

     <param-value>false</param-value>

   </jsp-param>

</weblogic-web-app>

The behavior of 

LoadBeforeAppDeployments

 in 

StartupClassMbean

 has changed 

between versions 6.x and 7.0 Service Pack 2. 

LoadBeforeAppDeployments

 still exists in version 7.0 Service Pack 2, but its 

behavior has changed. In 6.x, setting 

LoadBeforeAppDeployments

 to true caused 

startup classes to be invoked after the datasources were created and before the 
applications were activated. In 7.0 Service Pack 2, it determines whether a startup class 
is loaded and run before the server activates JMS and JDBC services or deploys 
applications and EJBs. 

A Managed Server running WebLogic Server 6.x cannot obtain its configuration and 
boot using an Administration Server running WebLogic Server 7.0. Make sure that you 
do not copy the 

running-managed-servers.xml

 file from your WebLogic Server 

6.x installation directory to your WebLogic Server 7.0 installation directory.