That is the correct behaviour. According to the JSP spec, the class
attribute must be "The fully qualified name of the class that defines
the implementation of the object." So you must include the full
package name.
--
Len Popp
[EMAIL PROTECTED]
http://www.lmp.dyndns.org/
On 10/20/06, Frederik G
From what I saw of the source the last time someone had trouble with
useBean, it uses reflection to come up with the class. The useBean tag
is a compiled class already and as such probably doesn't have any
knowlege of the import directive.
--David
Frederik Gottlieb wrote:
Thanks for the adv
Thanks for the advice, but lets leave the java.lang.String alone
(remember that it works if I fully qualify the package name)
I have a bean defined, dk.releaze.service.web.smsbulk.beans.Customer,
that is a public class with a public no-arg constructor with public
accessors and mutators - ie. a
The class specified in the useBean tag must be a valid bean.
java.lang.String is not a valid bean. Why don't you just use the
request attribute directly and omit the ? Example:
Login failed value is ${loginFailed}
Resin may be lax on this point, but tomcat 5.5 is a fair stickler on this.
Hi,
I'm new to Tomcat, but have been using Resin 2.1.16 for quite some time now.
We are in the process of upgrading our server software, and we would
like to test out the new Tomcat 5.5.20, but I seem to get some problems.
We are moving our existing (working) applications to a test server, now
