Jsp; Load Order For Startup Classes; Managed Servers - BEA WebLogic Server 7 Upgrade Manual

JSP

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
"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
<weblogic-web-app>
</weblogic-web-app>

Load Order for Startup Classes

The behavior of
between versions 6.x and 7.0 Service Pack 2.
LoadBeforeAppDeployments
behavior has changed. In 6.x, setting
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.

Managed Servers

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
6.x installation directory to your WebLogic Server 7.0 installation directory.
called
weblogic.xml
<jsp-param>
<param-name>printNulls</param-name>
<param-value>false</param-value>
</jsp-param>
LoadBeforeAppDeployments
running-managed-servers.xml
Additional Upgrade Procedures and Information
which is true by default, meaning that
printNulls
element in
printNulls
in
still exists in version 7.0 Service Pack 2, but its
LoadBeforeAppDeployments
BEA WebLogic Server 7.0 Upgrade Guide
weblogic.xml
StartupClassMbean
to true caused
file from your WebLogic Server
:
has changed
1-29