Bug 8605 - There is no setter method for property 'name'
Summary: There is no setter method for property 'name'
Status: CLOSED FIXED
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Application Taglib (show other bugs)
Version: 1.0
Hardware: PC other
: P3 critical with 1 vote (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-28 18:40 UTC by Michael Crawford
Modified: 2004-11-16 19:05 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Crawford 2002-04-28 18:40:09 UTC 
Been getting this. Never reported before. Just figured you had to know about 
this, since I'm getting it with Weblogic 6.1sp2 and doing nothing special. 

<Apr 28, 2002 11:31:12 AM PDT> <Error> <HTTP> <[WebAppServletContext
(4194486,fwm-test,/fwm-test)] Servlet failed with Exception
weblogic.servlet.jsp.JspException: (line 13): Error in using tag library 
uri='http://jakarta.apache.org/taglibs/application-1.0' prefix='app': There is 
no setter method for property 'name', for Tag 
class 'org.apache.taglibs.application.InitParametersTag'
        at weblogic.servlet.jsp.StandardTagLib.tld_jspException
(StandardTagLib.java:916)
        at weblogic.servlet.jsp.StandardTagLib.parseTagDD
(StandardTagLib.java:1050)
        at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:941)
        at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:207)
        at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
        at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY
(JspLexer.java:4187)
        at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4028)
        at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3875)
        at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2048)
        at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1862)
        at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1744)
        at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:1023)
        at weblogic.servlet.jsp.JspParser.doit(JspParser.java:80)
        at weblogic.servlet.jsp.JspParser.parse(JspParser.java:183)
        at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:119)
        at weblogic.utils.compiler.CodeGenerator.generate
(CodeGenerator.java:255)
        at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:327)
        at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:189)
        at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:154)
        at weblogic.servlet.internal.ServletStubImpl.getServlet
(ServletStubImpl.java:368)
        at weblogic.servlet.internal.ServletStubImpl.invokeServlet
(ServletStubImpl.java:242)
        at weblogic.servlet.internal.ServletStubImpl.invokeServlet
(ServletStubImpl.java:304)
        at weblogic.servlet.internal.ServletStubImpl.invokeServlet
(ServletStubImpl.java:200)
        at weblogic.servlet.internal.WebAppServletContext.invokeServlet
(WebAppServletContext.java:2495)
        at weblogic.servlet.internal.ServletRequestImpl.execute
(ServletRequestImpl.java:2204)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Comment 1 Glenn Nielsen 2002-11-10 15:24:31 UTC 
Thanks for reporting this.  This bug has been fixed and will be available
in the next nightly build and the Application 1.0.1 bug fix release when
it is made.  Sorry it took so long.