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!

Greetings
Stephan


Jock Fung schrieb:

> Hi,
>
>   When I use the following in the JSP using Tomcat 4.1.27, it doesn't
> work,
>
> <%@(protected).*" %>
> <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 seems not
> that useful
>
> <jsp:useBean id="user" class="com.bcit.beans.UserData"
> scope="session"/>
>
> It seems that the 'import' does not work properly? Is it true?
>
> Please advice.
>
> Thanks.
>
> Jock.
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> For additional commands, e-mail: tomcat-user-help@(protected)

--
Es wird immer weitergehen ---
--- Musik als Tr�ger von Ideen



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)