You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Thorsten Giesecke <th...@sourcepark.de> on 2003/02/25 14:22:18 UTC

Taglib: Unable to find setter method for attribute: required

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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Re: Taglib: Unable to find setter method for attribute: required

Posted by "David M. Karr" <dm...@earthlink.net>.
>>>>> "Thorsten" == Thorsten Giesecke <th...@sourcepark.de> writes:

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

    Thorsten> Unable to find setter method for attribute: required

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

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

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

If you haven't solved this yet, it could be useful to see your actual tag class
and the TLD.

There should be no problem with implementing a setter method in the base class,
as opposed to the derived class.

-- 
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
dmkarr@earthlink.net   ; SCJP; SCWCD




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org