Alex,
Until the expert group rules on this, one workaround (that will always work)
is to simply do the following (assuming a property of type Object):
instead of:
use:
Another way is to define a PropertyEditor associated with your
property of type Object.
As Craig men
Maya Muchnik wrote:
> Why you cannot use only one setter "public setIndex (String index)" and then inside
>check if the
> string is convertable to integer or not? This way your index can represent a number
>or "all".
In Tocmat 3.x, your suggestion works if the tag looks like:
OR
Why you cannot use only one setter "public setIndex (String index)" and then inside
check if the
string is convertable to integer or not? This way your index can represent a number or
"all".
"Craig R. McClanahan" wrote:
> Alex Tang wrote:
>
> > Thanks for the quick reply Craig.
> >
> > A follo
Alex Tang wrote:
> Thanks for the quick reply Craig.
>
> A followup question. In tomcat 3.1, I was able to do
>
> public setIndex ( Object o )
>
> If this is legal, I can do my own internal checking to see if the object "o" is a
>String or an
> int. However in Tomcat 4.0, I get an error w
This is how I think Taglib attrs work:
The jsp engine actually looks at your taglib class
and figures out that it needs to call a setXXX(int)
method because the "index" member variable is
declared as an int.
I don't know if there is
