input textarea compilation problem

[Nathan Maves <Na...@Sun.COM>]

I have a strange error when I compile my jsp within Sun Studio 4 (ide).

I get the following error :

newRequest.jsp [123:24] Unable to find setter method for attribute: 
attributesText
Errors compiling newRequest.


here is the code :

<input:textarea name="purpose" attributesText='cols="40" rows="5" 
wrap="virtual"'/>

In fact I get this message with all of the attributes of a textarea. 
The input tag lib works perfect for all of the other tags.  The code 
works once I depoly it but this is real pain for debugging.

I have sent some emails here within Sun and got that it has something to 
do with Bean Introspector.  I guess this is fixed in j2se 1.4.2 witch is 
not released yet.  Is there anything that we can to to fix this?  The 
email I got is attached below.  I guess the problem resides with the 
compiler confussing java.awt.TextArea with the tag TextArea.

Any ideas on a quick workaround?


Nathan


Attached is an email I got

Nathan Maves writes:
# I have a customer taglib from jakarta that will not complie in
# S1Studio4.  The same code when pushed to S1AS7 compiles and run perfect.
# [...] webapp using the input taglib from jakarta.

Hi Nathan,

this is a known problem which derives from a JDK bug. See issuezilla

http://www.netbeans.org/issues/show_bug.cgi?id=29657

Tomcat's JSP compiler looks for a Bean Introspector for the class
TextArea (the name of the Jakarta tag) but doesn't use the package
when it's looking so instead it finds the BeanInfo for
java.awt.TextArea (provided by the form editor).

The JDK bug id is 4750368. It was fixed for JDK 1.4.2, and we have
verified that this bug does not show up when using pre-release
versions of that. It will be release noted for Netbeans 3.5 and
presumably for the next S1S release also.

I can't tell from your message whether you are using S1S or Tomcat as
the default execution server (also the one that handles any
compilation prior to deployment, which was enforced in S1S4). While my
information comes from using the Tomcat plugin (JWSDP), S1AS uses the
JSP container from Tomcat and is likely to have the same problems with
compilation.

I don't think disabling the form editor is a viable work around,
because of a complex interdependency of that with other modules which
I believe did not get resolved.

For Tomcat, one option is to set the IDE integration to minimal (as
this means that the server does not request the IDE to compile the
JSP, and therefore does not have access to anything that is not in the
server's classpaths - a side effect of this is that the JSP debugger
is not enabled, and that it is not possible to see the generated
servlet for a JSP). I am not sufficiently familiar with the S1AS
plugin to know what the options are. What you need is to turn off
compilation prior to deployment.

Another workaround is to use JDK 1.4.2 when it is released.

Ana


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