Cannot resolve symbol error on bean tags with application migrated from V4.0.1 to V5.0
 Technote (troubleshooting)
 
Problem(Abstract)
Page compile errors and cannot resolve symbol errors are issued for bean tags if an application is migrated from IBM® WebSphere® Application Server V4.0.1 to WebSphere Application Server V5.0.
 
Cause
The generated code for WebSphere Application Server V4.01 for a useBean tag uses a Beans.instantiate instead of creating a new object with the default constructor. The following describes the V4.0.1 code generated when using the useBean tag:

beanId = (beanClass)Beans.instantiate(getClassLoader(),
"...BeanClassName...")

V5.0 uses the following code for the useBean tag:

beanId = new ...BeanClassName...();

WebSphere Application Server V4.0.1 generated JSP™ code for a useBean tag that has a bean class without a default constructor compiles successfully, but would fail at runtime if it did not find the bean within the specified scope or context.

WebSphere Application Server V5.0 generated JSP code for a useBean tag that has a bean class without a default constructor fails to compile.
 
Resolving the problem
Make sure the 'class' attribute is correctly coded in the application.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server for z/OS Migration z/OS 5.0 Enterprise
 
 


Document Information


Current web document: swg21188309.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Classloader
Operating system(s): z/OS
Software version: 5.0
Software edition:
Reference #: 1188309
IBM Group: Software Group
Modified date: Oct 26, 2004