Custom Tag problem - NoSuchMethodError at MyAttInfo
I am having the following problem when trying to use a taglibrary in my web
application. Does anybody know why I am having this problem?
Thanks,
Ozzie Gurkan
Mon Jan 08 16:55:30 GMT+05:00 2001:<I> <WebAppServletContext-mims> resolving
taglib uri '/mims/taglib' to taglib-location /WEB-INF/tlds/taglib.tld:
Mon Jan 08 16:55:30 GMT+05:00 2001:<E> <WebAppServletContext-mims> Servlet
failed with Exception
java.lang.NoSuchMethodError
at weblogic.servlet.jsp.MyAttInfo.<init>(StandardTagLib.java:34)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:280)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:1
46)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
1)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:118)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:154)
at
com.manheim.mims.core.control.web.MainServlet.doGet(MainServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
My entire application works great on my Win2000 machine, so I don't think I
am having problems with my setup of the taglib/JSP referencing. I have this
same application running now on Jboss, Orion, and Weblogic on Win2000.
Any other ideas?
Thanks,
Ozzie Gurkan
"MKH" <[email protected]> wrote in message
news:[email protected]...
> It is likely that the method name is a bit screwey
>
> How is it defined as in your TLD file and how are you calling it in your
> JSP?
>
> Is there a corresponding set<TLDMethodName> in your Java class?
>
>
> "Ozzie Gurkan" <[email protected]> wrote in message
> news:[email protected]...
> > I am having the following problem when trying to use a taglibrary in my
> web
> > application. Does anybody know why I am having this problem?
> >
> > Thanks,
> > Ozzie Gurkan
> > Mon Jan 08 16:55:30 GMT+05:00 2001:<I> <WebAppServletContext-mims>
> resolving
> > taglib uri '/mims/taglib' to taglib-location /WEB-INF/tlds/taglib.tld:
> >
> > Mon Jan 08 16:55:30 GMT+05:00 2001:<E> <WebAppServletContext-mims>
Servlet
> > failed with Exception
> >
> > java.lang.NoSuchMethodError
> >
> > at weblogic.servlet.jsp.MyAttInfo.<init>(StandardTagLib.java:34)
> >
> > at
> > weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:280)
> >
> > at
> >
>
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:1
> > 46)
> >
> > at
> > weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
> >
> > at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
> >
> > at
> > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
> >
> > at
> > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
> >
> > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
> >
> > at
> weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
> >
> > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
> >
> > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
> >
> > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
> >
> > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
> >
> > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
> >
> > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
> >
> > at
> > weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
> >
> > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
> >
> > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
> >
> > at
> >
>
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
> > 1)
> >
> > at
> >
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> > :118)
> >
> > at
> >
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> > l.java:154)
> >
> > at
> > com.manheim.mims.core.control.web.MainServlet.doGet(MainServlet.java:67)
> >
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> >
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> >
> > at
> >
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> > :123)
> >
> > at
> >
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> > l.java:761)
> >
> > at
> >
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> > l.java:708)
> >
> > at
> >
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> > Manager.java:252)
> >
> > at
> >
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
> >
> > at
> > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
> >
> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
> >
> >
> >
>
>
Similar Messages
-
Custom Tag Problem With iPlanet
Hi,
I've followed the instructions for creating Custom Tags located at: http://docs.iplanet.com/docs/manuals/enterprise/41/rn41sp9.html#18776. I'm using the examples provided and am still getting the:
org.apache.jasper.JasperException: Unable to open taglibrary /jsps/test-tags.jar : com.sun.xml.tree.TextNode
error. I've followed the instructions "Make sure you have the DOCTYPE in your taglib.tld..." but I still get the error.
iPlanet 4.1 Enterprise on Windows 2000
Any ideas?
Thanks in advance.Hey i am also getting the same error, please let me know if u had solved this problem. i have copied the error message below
[25/Feb/2002:15:00:46] info ( 260): JSP: JSP1x compiler threw exception
org.apache.jasper.JasperException: Unable to open taglibrary /jsps/test-tags1.jar : in is null
at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java:708)
at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:119)
at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:190)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1048)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1022)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1018)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:173)
at com.netscape.server.http.servlet.NSServletEntity.load(NSServletEntity.java:230)
at com.netscape.server.http.servlet.NSServletEntity.update(NSServletEntity.java:149)
at com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:453)
[25/Feb/2002:15:00:46] warning ( 260): Internal error: Failed to get GenericServlet. (uri=/web/jsps/test-tags.jsp,SCRIPT_NAME=/web/jsps/test-tags.jsp) -
Hello Everyone,
I am using iPlanet 4.1 as my web server and am having some problems with using custom tags. I try to access a jsp that uses my custom tags and I get a 500 Internal Server error. Then when I check the web server logs all it has is this one very esoteric message: "[26/Sep/2002:08:35:51] warning ( 8042): Internal error: Failed to get GenericServlet. uri=/BUYS/sep_accts.jsp,SCRIPT_NAME=/BUYS/sep_accts.jsp)" Usually I get this message when I make changes to a servlet and do not restart the web server, but that is not the problem this time.
I am trying to use a very simple tag called SayHelloTag which just prints hello to the browser. I have a foundation tag which extends tag support and then SayHelloTag extends the foundation tag. Then I have it all JARd up and in the classpath like I'm supposed to. If anyone could take a look at my code and tell me if you see anything wrong I would be most appriciative!
BuysFoundationTag
package com.nf.buys.tags;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import java.io.*;
import com.nf.buys.lists.*;
public class BuysFoundationTag extends TagSupport
SayHelloTag
package com.nf.buys.tags;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import java.io.*;
import com.nf.buys.lists.*;
public class SayHelloTag extends BuysFoundationTag
public int doStartTag()
{ System.out.println("Starting do Start tag");
try
System.out.println("start the try statement");
JspWriter out = pageContext.getOut();
System.out.println("output the hello message");
out.println("Say Hello");
catch(Exception e)
e.printStackTrace();
finally
return SKIP_BODY;
TLD File
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://cheerios2.nfs.nwie.net:5050/BUYS/web-jsptaglibrary_1_1.dtd">
<taglib>
<!-- after this the default space is "jsptaglibrary_1_2.dtd" -->
<tlibversion>1.0</tlibversion>
<jspversion>1.1</jspversion>
<shortname>buyslib</shortname>
<info>
A custom tag library for use by the Nationwide Financial,
Financial Systems, Automated Buy/Sell System.
</info>
<tag>
<name>SayHello</name>
<tagclass>com.nf.buys.tags.SayHelloTag</tagclass>
<bodycontent>JSP</bodycontent>
<info>A test tag</info>
</tag>
</taglib>
finally, my JSP page
<html>
<head>
<title>Automated BUY/SELL System</title>
<link rel=stylesheet href="buys_styles.css" type="text/css">
<%@ taglib uri="/BUYS/buys-tags.jar" prefix="buystag" %>
</head>
<body bgcolor='#FFFFF'>
<div id='heading'>
This is the heading information
</div>
<div id='navigation'>
<table width='100%'>
<tr>Nav Option 1</tr>
<tr>Nav Option 2</tr>
<tr>...</tr>
<tr>Nav Option n</tr>
</table>
</div>
<div id='optionalMessage'>
This is the optional message
</div>
<div id='listArea'>
<buystag:SayHelloTag>
</div>
</body>
</html>I get no compilation errors when I compile any of the tag handler classes. But when the web server can't compile the jsp page. Am I doing something obviously wrong? Please help!!
ChrisOMG I am a moron. I just have the name of the tag wrong.
-
I have implemented what I thought was a simple custom tag to handle if
conditions. In the page that I am using to test this new tag, I have
two instances of this tag - one right after another - the second of
which is giving me an error in parsing the page saying that there is a
close tag for which there is no start. The page looks like this:
<prefix:if expr="<%=expr here%>" >
<p>some text</p>
</prefix:if>
<prefix:if expr="<%=expr here%>" >
<p>some more text</p>
</prefix:if>
Where prefix is really the prefix I identified in my taglib directive
and "expr here" are two different boolean expressions.
I have search the page for an errant closing tag - but they are all
matched up just fine. At first I had these tags nested - and thinking
that was the problem - I unrolled the nesting so that the start and
end pairs were always matched up - i.e. an end for this tag always
came after the start without an intervening start for the same tag.
But doing that unrolling had no effect - and I always seem to get the
error on the second close tag being encountered by the parser.
My tld file specifies the body content for this tab as JSP and the
expr attribute as a run-time evaluated attribute which is required. My
tag class file extends TagSupport and implements the doStartTag and
setExpr() methods.
This problem occurrs for me running both WLS 5.1 SP5 and SP6.
Is there something simple that I am missing here? Note also that I
have two other custom tags which work just fine in the same page -
however both of those tags specify an empty bodycontent.
I found my problem - as I had thought I had a typo - I was missing the
'=' between expr and the quoted expression in the second tag. I sure
wish my eyes would quit filling in those missing pieces! :)
On Wed, 08 Nov 2000 13:21:47 GMT, [email protected] (Scott Jacobs)
wrote:
>I have implemented what I thought was a simple custom tag to handle if
>conditions. In the page that I am using to test this new tag, I have
>two instances of this tag - one right after another - the second of
>which is giving me an error in parsing the page saying that there is a
>close tag for which there is no start. The page looks like this:
>
><prefix:if expr="<%=expr here%>" >
> <p>some text</p>
></prefix:if>
><prefix:if expr="<%=expr here%>" >
> <p>some more text</p>
></prefix:if>
>
>Where prefix is really the prefix I identified in my taglib directive
>and "expr here" are two different boolean expressions.
>
>I have search the page for an errant closing tag - but they are all
>matched up just fine. At first I had these tags nested - and thinking
>that was the problem - I unrolled the nesting so that the start and
>end pairs were always matched up - i.e. an end for this tag always
>came after the start without an intervening start for the same tag.
>But doing that unrolling had no effect - and I always seem to get the
>error on the second close tag being encountered by the parser.
>
>My tld file specifies the body content for this tab as JSP and the
>expr attribute as a run-time evaluated attribute which is required. My
>tag class file extends TagSupport and implements the doStartTag and
>setExpr() methods.
>
>This problem occurrs for me running both WLS 5.1 SP5 and SP6.
>
>Is there something simple that I am missing here? Note also that I
>have two other custom tags which work just fine in the same page -
>however both of those tags specify an empty bodycontent.
-
Custom tag problem (parent/child tag)
I have a table tag and a column tag that I'm using in my application to display records.
The first time through it sets up headers and keeps a coun't of the columns.
The second time through it starts putting data in the fields. The problem I'm having is that I set a counter in the column tag. When it hits the first column it increments it from 0 to 1. When it hits the second column the counter has lost its value and is back to 0.
This only occurs if I have the align="Left". Or more precisely when some of the columns have align and some don't.... To fix this I can add align="right" to all the columns... but I have it defaulting to right and don't think I should have to include it.. can someone explain to me why this is occuring?
<xxx:table name="columnData" scope="request" scrollable="Yes">
<xxx:column key="selectorColumn:FILEID" title="Select" />
<xxx:column key="50" title="VTFHBRForm.de50" align="Left"/>
<xxx:column key="110" title="VTFHBRForm.de110" />
<xxx:column key="330" title="VTFHBRForm.de330" />
<xxx:column key="320" title="VTFHBRForm.de320" />
<xxx:column key="160" title="VTFHBRForm.de160" />
<xxx:column key="5" title="VTFHBRForm.de5" />
<xxx:column key="500" title="VTFHBRForm.de500" />
<xxx:column key="510" title="VTFHBRForm.de510" />
<xxx:column key="240" title="VTFHBRForm.de240" />
<xxx:column key="150" title="VTFHBRForm.de150" />
<xxx:column key="170" title="VTFHBRForm.de170" />
<xxx:column key="140" title="VTFHBRForm.de140" />
<xxx:column key="480" title="VTFHBRForm.de480" />
<xxx:column key="172" title="VTFHBRForm.de172" />
<xxx:column key="270" title="VTFHBRForm.de270" />
</xxx:table>u have not define what child tad retrieves (null?) or u mean to say EL is not evaluated...
because in my tag i had faced the problem for not evaluating the EL.
(although i had done rexp...=true).
could u put ur custom tag code then perhaps, i could say the solutiong -
Creating first custom tag, problems importing in WebSphere studio...
I'm trying to write a tag handler for my .tld file, but WebSphere won't recognize the following import statements:
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
TLD file:
<?xml version = "1.0" encoding = "ISO-8859-1"?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
"http://java.sun.com/dtd/Web-jsptaglibrary_1_2.dtd">
<taglib xmlns = "http://java.sun.com/JSP/TagLibraryDescriptor">
<tlib-version>1.0</tlib-version>
<jsp-version>1.2</jsp-version>
<short-name>Custom Tags Library</short-name>
<description>
Custom tags test.
</description>
<tag>
<name>customTags</name>
<tag-class>source.com.tags</tag-class>
<description>
formatted text box:
</description>
<attribute>
<name>mandatory</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
<name>optional</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
</tag>
</taglib>
- ls6vYou have to find the JAR(s) that contain the J2EE API (found in your Server download) and include them in the WebSphere classpath.
-
i was trying to run asample code that is using custom tag
that code is provided at
http://www.stardeveloper.com/articles/display.html?article=2001081801&page=1
after goin through steps when i executed the code i got this error
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.lang.NullPointerException
MyPackage.DataAccessTag.doAfterBody(DataAccessTag.java:73)
org.apache.jsp.DataAccessTag_jsp._jspService(org.apache.jsp.DataAccessTag_jsp:111)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)java.lang.NullPointerException
MyPackage.DataAccessTag.doAfterBody(DataAccessTag.java:73)
Go to line 73 of DataAccessTag (it will be in the doAfterBody method) and find what is null, why it is null, and either how to prevent it from being null or what to do in case it is null. -
Error processing CFX custom tag "CFX_iMSMail".
Hi
I am testing a CF application and this is the error I get.,
when I am trying to 'register for a certain event'.
Error processing CFX custom tag "CFX_iMSMail".
'The CFX custom tag "CFX_iMSMail" was not found in the custom
tag database. Please be sure to add custom tags to the database
before using them. If you have added your tag to the database then
you should check the spelling of the tag within your template to
insure that it matches the database entry.'
Text
The following are the lines of code in one of my cf pages
that seem to be responsible for causing the error.
486 : spooldir="#application.mailPath#/Out/"
487 : priority="0"
488 : smtpfrom="#listPart.contactEmail#"
489 : header_from="#Trim(listPart.contactName)#
<#Trim(listPart.contactEmail)#>"
Is there any fix for the CFX custom tag problem or is there
anything I am missing. I am using CF 7.0 on Windows XP
thanks in advanceYou must register CFX custom tags in the CF Administrator.
Until you do, they will not be found by the server. That's what the
error message is trying to tell you. -
Problem Calling Query in Custom Tag
I am using this code to call a custom tag called
broadcast.cfm
<cf_broadcast query="fe" orgID = "4">
The query fe is an included file on my site and is available
to the page I'm calling the custom tag from.
In the custom tag I am referencing the query like:
<cfloop query="#attributes.query#">
but I keep getting this error:
"The value of the attribute query, which is currently "fe",
is invalid. "
I must be missing something really simple here but can't
figure out what.quote:
Originally posted by:
-==cfSearching==-
rdk8487 wrote:
> In the custom tag I am referencing the query like:
> <cfloop query="#attributes.query#">
> but I keep getting this error:
> "The value of the attribute query, which is currently
"fe", is invalid. "
It is a scoping problem. The query is defined in the calling
page. To access it by name, within the custom tag, use the "caller"
scope.
<cfloop query="caller.#attributes.nameOfTheQuery#">
If the query object is passed to the custom tag via an
attribute you shouldn't need the caller scope. See attached sample. -
Custom Tag Capitalization Problem..
All,
OS: Windows 2000
App Server: Weblogic 6.0 sp 2
JDK: 1.3 (and tried 1.3.1)
I have a set of custom tags that run fine when I use them on an app server (such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which weblogic 6.x requires, they suddenly start generating errors with attributes which have capitalized letters in them. For example, in my taglib I have:
<attribute>
<name>closeConnection</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
and in the support class I have:
* Get the value of closeConnection.
* @return value of closeConnection.
public boolean getCloseConnection() {
return closeConnection;
* Set the value of closeConnection.
* @param v Value to assign to closeConnection.
public void setCloseConnection(String v) {
if(v.toUpperCase().equals("TRUE")){
this.closeConnection = true;
} else {
this.closeConnection = false;
When I go to the page that this tag is on, I get the following output:
Parsing of JSP File '/index.jsp' failed:
/index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks': There is no setter method for property 'closeconnection', for Tag class 'net.cwerks.taglib.MyTag'
probably occurred due to an error in /index.jsp line 1:
<%@ taglib uri="/cwerks" prefix="cwerks" %>
Thu Aug 02 19:06:52 PDT 2001
Note that the 'closeconnection' is all lowercase despite the fact that it is upper case in the tld and in the class itself.
I came across a similar problem in weblogic 5.1 when I upgraded from JDK 1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2, but a dll was missing. I also tried switching it to 1.3.1, but that did not help. It seems like introspection may have changed slightly between the two version. I'm shocked, and a bit suspicious, that I haven't seen this problem all over the newsgroups. Anyone else seen this?
Thank you,
Carson Gross
[email protected]
[att1.html]
A solution presents itself:
The problem was NOT with capitalization. Instead, the problem was as
follows:
My method was for setting a boolean, but I took a string so that people
wouldn't have to type:
<mytags:tag foo="<%=true%>" />
instead, they could type:
<mytags:tag foo="true" />
which would call the setter method with a string "true", which would be then
converted to a boolean within my class.
So my setter has this signature:
public void setFoo(String s)
and my getter has this signature:
public boolean getFoo() /* I know this isn't standard, but isFoo doesn't
sound good to me*/
I can't tell if it's because JavaBeans changed slightly between jdk 1.2.2
and 1.3.x, or if Weblogic changed the way that they do things (I suspect the
latter, since I had things working fine in WL 5.2 w/ jdk 1.2.2 and then
things broke with WL 5.2 w/ jdk 1.3), but this no longer returns foo as a
valid property to be set, and since weblogic 6.x relies on JavaBeans,
instead of straight up introspection, it barfs. (I found this out by using
jad/emacs, a wicked combination for those who want to poke around in jars).
Anyway, I hope I can save someone else who has this same, albeit
specialized, problem a lot of pain by my discovery. Your getters and
setters better be of the same type with custom tags, or weblogic w/ jdk1.3.x
is gonna barf when parsing the tld.
Cheers, and thank God that's behind me,
Carson Gross
[email protected]
====================================================
"Carson Gross" <[email protected]> wrote in message
news:[email protected]...
The plot grows thicker...
The tags work fine on Tomcat 3.2.2
I deploy the example tags that came with wl60 that have more than one
capital letter in thier attributes, and they work fine. But my tag library
stubbornly insists on not working so long as I keep the attributes with more
than one capital letter in. If I remove the offending attributes, or change
them to have only one capital letter, they work, but this is not an
acceptable solution. (I guess.)
I even created an simple introspection class to make sure that the acutal
methods were there. They were.
I am at a complete loss here... I guess it's tomcat for now.
Cheers,
Carson Gross
[email protected]
"Carson Gross" <[email protected]> wrote in message
news:[email protected]...
All,
OS: Windows 2000
App Server: Weblogic 6.0 sp 2
JDK: 1.3 (and tried 1.3.1)
I have a set of custom tags that run fine when I use them on an app server
(such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which
weblogic 6.x requires, they suddenly start generating errors with attributes
which have capitalized letters in them. For example, in my taglib I have:
<attribute>
<name>closeConnection</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
and in the support class I have:
* Get the value of closeConnection.
* @return value of closeConnection.
public boolean getCloseConnection() {
return closeConnection;
* Set the value of closeConnection.
* @param v Value to assign to closeConnection.
public void setCloseConnection(String v) {
if(v.toUpperCase().equals("TRUE")){
this.closeConnection = true;
} else {
this.closeConnection = false;
When I go to the page that this tag is on, I get the following output:
Parsing of JSP File '/index.jsp' failed:
/index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks':
There is no setter method for property 'closeconnection', for Tag class
'net.cwerks.taglib.MyTag'
probably occurred due to an error in /index.jsp line 1:
<%@ taglib uri="/cwerks" prefix="cwerks" %>
Thu Aug 02 19:06:52 PDT 2001
Note that the 'closeconnection' is all lowercase despite the fact that it is
upper case in the tld and in the class itself.
I came across a similar problem in weblogic 5.1 when I upgraded from JDK
1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2,
but a dll was missing. I also tried switching it to 1.3.1, but that did not
help. It seems like introspection may have changed slightly between the two
version. I'm shocked, and a bit suspicious, that I haven't seen this
problem all over the newsgroups. Anyone else seen this?
Thank you,
Carson Gross
[email protected]
-
Custom Tags starting with $: lots of problems
I'm building an extension for MovableType template tags.
Those tags can be delimited in several ways: <MTNameOfTheTag>
or <$MTNameOfTheTag> or even <$MTNameOfTheTag$>. Since
the dollar sign is not allowed as tag name, i put a
prefix="<$" in tag definition, but now i have some problems:
1. even if in tag chooser i can see the dollar-prefixed tags,
i cannot see them in code hints (I mean "automatic" code hints,
those floating menus automatically made for every tag/every
attribute/every enumerated attriboption in library).
2. I tried to manually code tags in codehints.xml file with
the "<$ pattern (so i can change the icon associated to my
custom tags, too. That's will be very elegant) but I loose "child"
codehints menus: the first codehints menu (the one i manually made)
comes up, but those for attributes and attributes values don't.
3. With the solution in point 2 not only i loose "automatic"
codehints, but i have to write THREE files for every tag
(taglibrary, codehins, third party tags file). Lot of time :/
4. Dollar signs, in both start and end, are NOT part of the
name, but part of the tag, like a prefix or a suffix. With an
attribute i should have:
<$MTBlogName donald="goofie"$>
and not:
<$NTBlogName$ donald="goofie">
as actually i have
so, as i said...a lot of problems! i hope someone can help
me...its really an hard sunday, today! :/
tnx in advanceI think you might be moving into creating your own server
model.
Just a thought. -
Problem with custom tag attribute types
Hi,
I try to figure out how to pass an attribute to a custom tag that is of a type other than "String"?
In my case, I should pass an attribute with a type of "java.util.ResourceBundle".
My tag looks like this:
<tt:cs sel="ab" ce="<%= java.util.ResourceBundle.getBundle("de", Application.getApp().getLocale())%>" />
I always get the message that the attribute ce is empty.
Isn't it possible to have attirbutes that are of an other type than string? How could I solve this problem?
Thanks a lot!
Regards PatrickIn JSP 1.2, in the Tag Library Descriptor, you can specify a tagt attribute as
<attribute>
<name>attr1</name>
<required>true|false|yes|no</required>
<rtexprvalue>true|false|yes|no</rtexprvalue>
<type>fully-qualified_type</type>
</attribute> Notice the XML element <type>fully-qualified_type</type>
Not sure if you can do this in JSP 1.1 -
Custom Tag -- Custom Component problems with iframes
I have a "project" component that originally iterated over a list of models and created/renderered the corresponding (and fairly complex) interactive UI components for those models. On the client-side, the output from these were then organized neatly into "tabs" via CSS ... all on one page. Since these UI Components are so hefty, when any iteraction was done on one of them, the whole page had to re-render and things got just plain slow. To get around this limitation, I decided to have my "project" component no longer create the UI components himself, but instead generate an IFRAME that points to a page that will generate a single component. This way, any iteraction will just cause that single IFRAME to refresh.
Due to the fact that an IFRAME can only be populated by using the src attribute, I have created a page that contains a JSF View (<faces:view>) and inside is a single custom tag of mine (<mine:displayView>). Let's call this page singleDisplayView.jsf. I create iframes that point to singleDisplayView.jsf with different request params for each (singleDisplayView.jsf?modelName=Foo, singleDisplayView.jsf?modelName=Bar, etc.)
The displayView tag has one attribute called requestQueryString and I use the tag like so:
<t:displayView requestQueryString="<%=request.getQueryString()%>" />The displayView tag's class is DisplayViewTag. In DisplayViewTag::setProperties(UIComponent uiComponent) method, I get the model name out of the request map and set this property on the UIComponent.
The problem is that I'm noticing that as the main page (that contains these frames) loads, setProperties() is only being called twice. After that, the components created by subsequent iframes just seem to be using the modelName from the second frame.
Is there a syncronization issue I don't understand?
Any ideas?
Any help would be much appreciated.
Thanks in advance,
MarkOn a possibly related note, I read this in an article of the JSF application lifecycle:
In the first phase of the JSF lifecycle -- restore view -- a request comes
through the FacesServlet controller. The controller examines the request and
extracts the view ID, which is determined by the name of the JSP page.Could it be that the lifecycle is trying to reuse components from a single view, since all these iframes are pointing to the same page? -
Taglib problem: Cannot parse custom tag with short name table
Hello!
I am having problems deploying a jsp tag in web as. The same war file works fine on websphere, jboss. SAP web as seems to be complaining about the short name in the tld.
Can any body me to any known web as issues with jsp tags?
Thanks
[code]
Application error occurs during processing the request.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page /usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/dispear/servlet_jsp/disp/root/test.jsp.
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:85)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:207)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:369)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Cannot parse custom tag with short name table.
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:129)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ElementCollection.action(ElementCollection.java:52)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:307)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:74)
... 18 more
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Unknown class name java.lang.Object.
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.convertString(TagBeginGenerator.java:365)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:187)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:212)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:269)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:127)
... 21 more
[/code]Hi Ray,
I am facing similar kind of issue.
Can you please help to resolve it?
Thanks in advance.
Logs are as below [Here I am using standard tag lib]::
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name [out].
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:183)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspIncludeDirective.action(JspIncludeDirective.java:51)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:69)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.GenerateJavaFile.generateJavaFile(GenerateJavaFile.java:72)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:270)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.generateJavaFile(JSPProcessor.java:194)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:126)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassName(JSPChecker.java:319)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.compileAndGetClassName(JSPChecker.java:248)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassNameForProduction(JSPChecker.java:178)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.processJSPRequest(JSPChecker.java:109)
at com.sap.engine.services.servlets_jsp.jspparser_api.JspParser.generateJspClass(JspParser.java:154)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:193)
... 47 more
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Attribute [value] of [<c:out>] can accept only static values.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.calculateAttributeValue(TagBeginGenerator.java:476)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:394)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:562)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:678)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:181)
... 64 more
Regards,
Sankalp -
JSF custom tag body content problem
Hi, I'm having some problem with a custom tag I built, but the body of the tag content is not rendered correctly.
I have:<foo:bar>
<ul>
<li>blah</li>
<li>blah</li>
</ul>
</foo:bar>
</pre>But the rendered html source look like this: <ul>
<li>blah</li>
<li>blah</li>
</ul>
<!-- beging foo tag -->
<!-- end foo tag -->The <ul> tags are supposed to be inside of the <!-- begin foo --> & <!-- end foo -->. I've declared in TLD it has JSP content. I've compared to the J2EE tutorial and corejsp book again and again, couldn't figure where I went wrong. So, am I missing something?
Thanks a lot.Use <f:verbatim> around the non-jsf content.
I.e.<foo:bar>
<f:verbatim>
<ul>
<li>blah</li>
<li>blah</li>
</ul>
</f:verbatim>
</foo:bar>--
Sergey : jsfTutorials.net
Maybe you are looking for
-
SOA 11.1.1.3.0 - Connection Pool has been suspended during weak load
Hi, I have a SCA with different BPEL, all uses several db adapters. Each db adapter has retry count set to 1. Each bpel has the following properties: <property name="bpel.config.transaction" many="false">required</property> <property name="bp
-
How to transfer my PDF files from computer to iphone 5s
How to transfer my PDF files from my laptop to my iPhones 5 s and how to make folder to store those files?
-
Photo stream will not transfer photos from mac to iphone
I downloaded the new iOS8 software for me iPhone, and now my photo stream isn't working. It sends the pictures i take on my phone to the mac, but won't send the pictures from the mac to the iPhone. I take a lot of pictures on a camera and need them
-
PHP/MySQL incommunicado since upgrading OS X Server 10.4.2 - 10.4.3
Back when 10.4 first came out and I foolishly upgraded my server right away, I spent hours trying to reconfigure PHP because Apple had monkeyed with with the configuration (since 10.3) and shipped it such that PHP/MySQL wouldn't speak out of the box.
-
hello we are experiencing an very frustrating problem. we are burning a Dual Layer disk with a one hour video, and a slide show. We have followed all of the pointers listed here about compatible file types and audio files. When we go to burn the disk