After changing from Tomcat 3.2.3 to Tomcat 4.1.18 the following
exception occurs:

Unable to find setter method for attribute: required

The TLD defines the required attribute as optional,
the setter method (setRequired(String ...)) is available
and with Tomcat 3.2.3 there are no problems.

Are there any changes in the JSP/Taglib definition, which
permits the use of required as an attribute name?

Is it required, that every taglib class has it's own setter
method or can i use an abstract parent class which implements
this setter method once? can this result in problems with
introspection?


thanks for any help
thorsten


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to