Hi Jock,
afaik, the class attribute always requires a FULL qualified classname of
the bean to construct. This is independent of the import directive.
This is the same behavior as the standard Java Class.forName(...) method.
In fact this is exact the way how the jsp:useBean tag is compiled!
Hi,
When I use the following in the JSP using Tomcat 4.1.27, it doesn't
work,
%@ page import=com.bcit.beans.* %
jsp:useBean id=user class=UserData scope=session/
but I need to specify in the class comand the actual path, then it can
find UserData in the path. I can remove the page tag and it
]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 2:18 AM
Subject: JSP import command
Hi,
When I use the following in the JSP using Tomcat 4.1.27, it doesn't
work,
%@ page import=com.bcit.beans.* %
jsp:useBean id=user class=UserData scope=session/
but I need to specify in the class comand
