Hi,
Has anyone seen this before:
8-01 16:51:50:739 - (E) SMSActionServlet Thread [ExecuteThread: '11' for
queue: 'default']; Exception
[weblogic.servlet.jsp.JspException: (line 3): Error in using tag library
uri='/WEB-INF/struts-html.tld' prefix='struts': The Tag class
'org.apache.struts.taglib.html.BaseTag' has no setter method corresponding
to TLD declared attribute 'target', (JSP 1.1 spec, 5.4.1)
at
weblogic.servlet.jsp.StandardTagLib.tld_jspException(StandardTagLib.java:257
)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:389)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:2
67)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:234)
02-08-01 16:51:50:740 - (E) SMSActionServlet Thread [ExecuteThread: '11' for
queue: 'default']; Unexpected exception:(line 3): Error in using tag library
uri='/WEB-INF/struts-html.tld' prefix='struts': The Tag class
'org.apache.struts.taglib.html.BaseTag' has no setter method corresponding
to TLD declared attribute 'target', (JSP 1.1 spec, 5.4.1)
It seems like the jsp1.1 spec says you must have get & set method for a jsp
Tag class. The struts classes do not (as in the above example BaseTag has
an attribute of target in its TLD file but no setTarget(String target)
method... So when weblogic tries to resolve the tag library struts-html.tld
it falls over!
I don't know how to get around this, other than adding set and get methods
in every struts src file and rebuilding which could take quite a while -:)
Does anyone else have any ideas? or has anyone seen this before?
Thanks
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
