Tag library issue

Hi All,
I am getting the following error when I try to use the tag library in my JSP page
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1,
<%@ taglib uri="/WEB-INF/test_tags.tld" prefix="test" %>
It seems that it is not able to parse the tld file. Has anybody run into similar issue? What is the solution?
Thanks in advance.

Rahul -
It's hard to say what the problem is without seeing the tld, but by default, the .tld file should be located in the META_INF directory, not WEB_INF.
Hope this helps,
Lynn
Java Tools Team

Similar Messages

Struts Issue - Exception in Servlet - Potential Tag library issues

Hi,
We are using the Struts framework in our application and we run into the following exception.
/Jul/2005:16:16:11] SEVERE ( 2412): ApplicationDispatcher[eCATS] Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException
at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:478)
at jasper.summary._su_Desktop_jsp._jspService(_su_Desktop_jsp.java:4708)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:552)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:368)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:287)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:757)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:123)
at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:374)
at com.ams.action.AMSRequestProcessor.processAMSActionForward(AMSRequestProcessor.java:814)
at com.ams.action.AMSRequestProcessor.processAMSRequest(AMSRequestProcessor.java:365)
at com.ams.action.AMSRequestProcessor.process(AMSRequestProcessor.java:144)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1209)
at com.ams.action.AMSActionServlet.service(AMSActionServlet.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:757)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:123)
at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:374)
at com.ams.action.AMSRequestProcessor.processAMSActionForward(AMSRequestProcessor.java:814)
at com.ams.action.AMSRequestProcessor.processAMSRequest(AMSRequestProcessor.java:365)
at com.ams.action.AMSRequestProcessor.process(AMSRequestProcessor.java:144)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1209)
at com.ams.action.AMSActionServlet.service(AMSActionServlet.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(Stan
[21/Jul/2005:16:16:11] SEVERE ( 2412): dardHostValve.java:203)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:856)
----- Root Cause -----
javax.servlet.jsp.JspException
at org.apache.struts.taglib.logic.CompareTagBase.condition(CompareTagBase.java:177)
at org.apache.struts.taglib.logic.NotEqualTag.condition(NotEqualTag.java:46)
at org.apache.struts.taglib.logic.ConditionalTagBase.doStartTag(ConditionalTagBase.java:174)
at org.apache.struts.taglib.nested.logic.NestedNotEqualTag.doStartTag(NestedNotEqualTag.java:52)
at jasper.summary._su_Desktop_jsp._jspService(_su_Desktop_jsp.java:2499)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:552)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:368)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:287)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:757)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:123)
at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:374)
at com.ams.action.AMSRequestProcessor.processAMSActionForward(AMSRequestProcessor.java:814)
at com.ams.action.AMSRequestProcessor.processAMSRequest(AMSRequestProcessor.java:365)
at com.ams.action.AMSRequestProcessor.process(AMSRequestProcessor.java:144)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1209)
at com.ams.action.AMSActionServlet.service(AMSActionServlet.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:757)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:123)
at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:374)
at com.ams.action.AMSRequestProcessor.processAMSActionForward(AMSRequestProcessor.java:814)
at com.ams.action.AMSRequestProcessor.processAMSRequest(AMSRequestProcessor.java:365)
at com.ams.action.AMSRequestProcessor.process(AMSRequestProcessor.java:144)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1209)
at com.ams.action.AMSActionServlet.service(AMSActionServlet.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.
Anyone ever encountered this one or has a solution for this.
Thanks
Shekhs

take a look at this this

Logging issue with rssutils.tld Tag Library

I'm using the rssutils.tld tag library to display three RSS feeds on my application's JSP homepage. It works very very well and I'm quite happy with the results (I'm running on a Tomcat 5.5.7 server). I implemented the solution following the examples in the tutorial at http://java.sun.com/developer/technicalArticles/javaserverpages/rss_utilities
The only problem I'm having though is in my Tomcat logs. Whenever a user loads my home page, a ton of tags are written to my tomcat stdout log:
<rss>
<channel>
<title>
</title>
<link>
</link>
<description>
</description>
<language>
</language>
<copyright>
</copyright>
and so on for several hundred lines. This not only fills up my logs very very quickly, I'm worried about performance. Has anyone run into this problem and, if so, have a suggestion on how to have the tag library only log errors instead of every tag it processes? Thanks in advance.

There are 2 System.out's in com/sun/cnpi/rss/handlers/DocumentHandler.class For test purposes I commented these out and it resolved the issue. I think the license allows modifications and redistribution as long as the copyright notice is included but I am no expert on legal stuff. If someone can assist me with this I would be happy to provide the modified package.

Custom tag lib issue with task flow in portal

Dear Experts,
I am facing an issue and need your guidance
I have a ADF task flow which is consumed in portal. My task flow uses a custom tag library.
When I run the task flow on portal I am facing following issue:
Caused by: oracle.jsp.parse.JspParseException:
Error: Encountered deferred syntax #{ in template text. If intended as a literal, escape it or set directive deferredSyntaxAllowedAsLiteral
at oracle.jsp.parse.JspParseTagXMLTextContainer.processAttributeForELFunctions(JspParseTagXMLTextContainer.java:118)
at oracle.jsp.parse.JspParseTagXMLTextContainer.processAttributeValue(JspParseTagXMLTextContainer.java:103)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1565)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:886)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTagFile.parseXMLSrc(JspParseTagFile.java:341)
at oracle.jsp.parse.JspParseTagFile.parse(JspParseTagFile.java:256)
at oracle.jsp.parse.OracleJsp2Java.transformImpl(OracleJsp2Java.java:439)
at oracle.jsp.parse.OracleJsp2Java.transform(OracleJsp2Java.java:593)
at oracle.jsp.runtimev2.JspPageCompiler.attemptCompilePage(JspPageCompiler.java:691)
at oracle.jsp.runtimev2.JspPageCompiler.compileBothModes(JspPageCompiler.java:490)
at oracle.jsp.runtimev2.JspPageCompiler.parseAndGetTreeNode(JspPageCompiler.java:457)
at oracle.jsp.runtimev2.JspPageInfo.compileAndLoad(JspPageInfo.java:624)
at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:645)
... 120 more
<XmlErrorHandler> <handleError> ADF_FACES-60096:Server Exception during PPR, #1

Hi,
Make sure you have the JSTL tag library selected in you deployment plan. Go to Project Properties->Deployments->your_deployment_profile->WWB-INF/Lib Contributors and check JSTL.
Let me know if this worked for you!
Regards,
Mihai

Custom tag library called multiple times

Hi ppl ,
I have a custom tag library which i use to populate some menu components. When i do call my custom tag library though , it is called multiple times, use case is as follows.
I have menu tabs and menu bars which thanks to Mr.Brenden is working splendidly as so:-
<af:menuTabs>
<af:forEach var="menuTab" items="#{bindings.menu.vwUserMenuTabRenderer.rangeSet}">
<af:commandMenuItem text="#{menuTab.MenuLabel}"
shortDesc="#{menuTab.MenuHint}"
rendered="true"
immediate="true"
selected="#{sessionScope.selectedMenuId == menuTab.MenuId }"
onclick="fnSetSelectedValue('#{menuTab.MenuId}')" >
</af:commandMenuItem>
</af:forEach>
</af:menuTabs>
<af:menuBar>
<af:forEach var="menuBar" items="#{bindings.menu.vwUserMenuBarRenderer.rangeSet}">
<af:commandMenuItem onclick="return clickreturnvalue()"
onmouseover="dropdownmenu(this, event,#{menuBar.MenuId}, '150px')"
onmouseout="delayhidemenu()"
text="#{menuBar.MenuLabel}"
action="#{menuBar.MenuUri}"
rendered="#{menuBar.ParentId == sessionScope.selectedMenuId}"
immediate="true" />
</af:forEach>
</af:menuBar>
</afc:cache>
now all of this code is within a subview , and just directly below the subview tag , i have the call to my custom tag library:-
<myCustomTagLib:menuCascade />
only issue now is that assuming i have in all 7 menu bar components, the doStartTag is called 7 times. the relevant code within my custom tag class is as follows :-
public int doStartTag() throws JspException {
return (EVAL_BODY_INCLUDE);
public int doEndTag() throws JspException {
try {
declareVariables();
return EVAL_PAGE;
}catch (Exception ioe) {
throw new JspException(ioe.getMessage());
and within my declareVariables method i do an out of the jscript ( out.print(jscript.toString()); ) which is a simple string generated based on certain conditions...
now it seems to be working fine on the front end , but when i view the source of the page, i notice that the declaration is called multiple times, and this happens because the doStartTag method is called multiple times, i haven't even nested the call to the custom tag within the menu components , any clue as to whats going wrong ?
Cheers
K

Hi,
if you add the following print statement
System.out.println("rendering "+FacesContext.getCurrentInstance().getViewRoot().getViewId());
Then the output in my case is
07/04/24 08:14:04 rendering /BrowsePage.jsp
07/04/24 08:14:05 rendering /otn_logo_small.gif
The image comes from the file system, which means it is rendered by the JSF lifecycle. If you reference the image with a URL then the lifecycle doesn't render the image but only refrences it.
To avoid your prepare render code to be executed multiple times, just check for jsp and jspx file extensions, which will guarantee that your code only executes for JSF pages, not for loaded files.
The reason why this happens is because the JSF filter is set to /faces , which means all files that are loaded through that path
Frank

Error while parsing the Tag Library Descriptor

Hi,
We are installing LC ES2 on Suse64 / weblogic platform. When the adobe-conmtentservices application is starting, we see a lot od error like this:
<Mar 24, 2010 10:56:53 AM CET> <Warning> <HTTP> <BEA-101196> <[/contentspace]: Error while parsing the Tag Library Descriptor at "/opt/oracle/product/WLS1031/user_projects/domains/LC9/servers/LC9_MS/tmp/_WL_user/adobe- contentservices/4xxkue/war/WEB-INF/contentservices.tld".
com.ctc.wstx.exc.WstxIOException: Tried all: '1' addresses, but could not connect over HTTP to server: 'java.sun.com', port: '80'
 at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683)
 at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086)
 at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHelper.java:134)
 at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:380)
 at weblogic.servlet.internal.TldCacheHelper.parseTagLibraries(TldCacheHelper.java:65)
 Truncated. see log file for complete stacktrace
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'java.sun.com', port: '80'
 at weblogic.net.http.HttpClient.openServer(HttpClient.java:314)
 at weblogic.net.http.HttpClient.openServer(HttpClient.java:404)
 at weblogic.net.http.HttpClient.New(HttpClient.java:240)
 at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:172)
 at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:356)
 Truncated. see log file for complete stacktrace
The application tries to download something from java.sun.com site but the server can not access internet. The process is repeated for each TLD file !
After a very time (more than 45 minutes!), the server finally starts and all adobe application are active
So, how to correct this behaviror ? is there a patch?
cb.

Hi,
Did you get solution for this because I am also facing same issue. Please do reply ASAP... it is very uegent.
Regards,
Srujan

Unable to add Custom JSP 1.2 Tag Library to Project

I am trying to upgrade to a newer version of JDeveloper (10.1.3.0.4) but am having a problem with projects that use custom JSP tag libraries.
After converting the project (.jpr) files to the new version, I double click and go to "JSP Tag Libraries." When I click on "Add" to add a new JSP Tag library, only JSP version 1.1 libraries are shown, I cannot choose any JSP 1.2 tag libraries.
my TLD files are all JSP 1.2, so I am not quite sure why this isn't working in a newer JDeveloper after it has worked fine in the past. If I examine any JSP page that uses my taglibs, I see the following 2 kinds of error:
the line:
<%@ taglib uri="taglib.uri" prefix="mytag" %>
is underlined in red and says "the tag library taglib.uri is referenced, but not installed"
And for any lines that try to use the custom tag:
<mytag:dosomething>
there is a yellow/orange underline that says "no grammar available for namespace taglib.uri, contents of element dosomething cannot be validated"
Note that I can add the taglib JAR file under Tools > Manage Libraries, but I cannot add the JSP tag library to my project. Is there some sort of compatibility issue when transferring project files from an old version of JDeveloper?
Any help would be appreciated

Yes any new project I create I can specify JSP 1.2 or 2.0 with the wizard and it works fine.
But I don't want to re-create my entire project file again just to register my taglibs.
Here's the JSP related section in web.xml:

<taglib>
<taglib-uri>taglib.uri</taglib-uri>
<taglib-location>/WEB-INF/tlds/mytag.tld</taglib-location>
</taglib>
It's definately something in the project itself... but I am lost as to what it is.
Edit: nvm I fixed it. It was the web.xml. I had to change the line:
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
into
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
and it worked. Thanks.
Message was edited by:
user523020

Custom Tag Library - error in IWS

My environment: Solaris 2.7, IWS4.1 SP3.
I currently try to run the Custom Tag Library example from IWS itself in
server_root/plugins/samples/servlets/taglibs. I follow the instructions to
config the IWS but fail to run the example. I turn on JSP debugging and
find the following error messages:
[12/Oct/2000:13:03:10] info (28609): Service(): uri=/jsps/test-tags.jsp
cgiScriptName=/jsps/test-tags.jsp token=null cached=false
[12/Oct/2000:13:03:10] info (28609): Internal Info: loading servlet
/jsps/test-tags.jsp
[12/Oct/2000:13:03:10] info (28609): JSP: This is a jsp 1.x file
[12/Oct/2000:13:03:10] info (28609): JSP: Before JSP1x compiler.compile,
servletName = /jsps/test-tags.jsp servletPath =
/u01/devin/docs/jsps/test-tags.jsp & dir = ../ClassCache
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Package name is:
jsps.jsps
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Class name is:
test0002dtags_jsp
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Java file name is:
/opt/netscape/server4/https-devin/config/../ClassCache/_jsps/_jsps/_test_000
2dtags_jsp.java
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Class file name is:
/opt/netscape/server4/https-devin/config/../ClassCache/_jsps/_jsps/_test_000
2dtags_jsp.class
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace:
Handling Directive: page {language=java}
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Accepted
org.apache.jasper.compiler.Parser$Directive at /jsps/test-tags.jsp(0,0)
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace:
Handling Directive: taglib {uri=/jsps/test-tags.jar, prefix=tt}
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Copying
/jsps/test-tags.jar into
/opt/netscape/server4/https-devin/config/../ClassCache//jsps/test-tags.jar
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Adding jar
/opt/netscape/server4/https-devin/config/../ClassCache//jsps/test-tags.jar
to my classpath
[12/Oct/2000:13:03:10] info (28609): Aborting JVM
[12/Oct/2000:13:03:10] info (28609): Exiting JVM due to: jvm_abort () and
jvm.exitOnAbort > 0
[12/Oct/2000:13:03:10] info (28609): JVM exit statistics:
AttachedThreads/Max=1/1, ActiveThreads/Max=1/1
[12/Oct/2000:13:03:11] info (28716): Initializing MMapSession Manager to
hold a maximum of (1000) sessions, each of which can store a maximum of
(100) values and no value size bigger than (1024) bytes, with a timeout
value of (1800) seconds
IWS keeps aborting JVM and one can see from the log that it abort jvm when
trying to :
[12/Oct/2000:13:03:10] info (28609): JSP1x Jasper Trace: Adding jar
/opt/netscape/server4/https-devin/config/../ClassCache//jsps/test-tags.jar
to my classpath
[12/Oct/2000:13:03:10] info (28609): Aborting JVM
I have tried another much simple Custome Tag Library example that only contain a simple tag that do output to page, but still getting the same error.

I had the same issue with WAS 6.1.0.2. I do not have a solution, but a workaround. I hope the workaround I have works for you too.
In my case, I have the TLD files deployed in a jar. So, the JSP 2.0 container is supposed to read those TLD files from the jar file. Since that was not happening, I extracted the TLD file from the jar file and placed it under my web project's WEB-INF folder.
I restarted my server and after that it worked.
Look at the IBM site to see if they have come up with a patch for WAS 6.0.
Hope this helps.
-Javier

ISA JSP tag library

I'm working with an ISA jsp and have some questions about the <isa:iterate> tag. For example does it work with a JCO.Table object? and if so, what other kinds of tables can it use?
Can anybody point me to some documentation on this tag library?
Thanks,
Brent

Hi,
I assume you are using ISA 4.0. You can use "com.sapmarkets.isa.core.util.table.ResultData" class with isa:iterate tag. You can read "ISA dev and ext guide" for this issue.
Best regards,
Altug Bayram

No tag library could be found with this URI - MyFaces with weblogic 9.2

I am deploying an application written using MyFaces(JSF1.1) + Tiles in weblogic 9.2. I am getting the following error when I acess any page..
Time[2009-01-28 02:02:33,039] [ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'::: ERROR javax.faces.webapp._ErrorPageWriter - - Message[-An exception occurred]
javax.faces.FacesException
 at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.renderTilesView(JspTilesTwoViewHandlerImpl.java:126)
 at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.renderView(JspTilesTwoViewHandlerImpl.java:110)
 at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
 at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216)
 at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
 at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:146)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:147)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
 at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: org.apache.tiles.TilesException: Error including path '/template/template.jsp'. Failed to compile JSP /template/template.jsp
template.jsp:1:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://richfaces.org/rich" prefix="rich"%><%@ page contentType="text/html;charset=UTF-8" language="java" %>
^----^
template.jsp:1:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://richfaces.org/rich" prefix="rich"%><%@ page contentType="text/html;charset=UTF-8" language="java" %>
^----^
template.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
^----^
template.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
^----^
template.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
^----^
template.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
^----^
template.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
^----^
template.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
^----^
template.jsp:5:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://tiles.apache.org/tags-tiles" prefix="tiles" %>
^----^
template.jsp:5:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://tiles.apache.org/tags-tiles" prefix="tiles" %>
^----^
 at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:427)
 at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
 at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.renderTilesView(JspTilesTwoViewHandlerImpl.java:124)
 ... 22 more
Caused by: java.io.IOException: Error including path '/template/template.jsp'. Failed to compile JSP /template/template.jsp
template.jsp:1:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://richfaces.org/rich" prefix="rich"%><%@ page contentType="text/html;charset=UTF-8" language="java" %>
^----^
template.jsp:1:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://richfaces.org/rich" prefix="rich"%><%@ page contentType="text/html;charset=UTF-8" language="java" %>
^----^
template.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
^----^
template.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
^----^
template.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
^----^
template.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
^----^
template.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
^----^
template.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
^----^
template.jsp:5:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://tiles.apache.org/tags-tiles" prefix="tiles" %>
^----^
template.jsp:5:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="http://tiles.apache.org/tags-tiles" prefix="tiles" %>
^----^
 at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:201)
 at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
 at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
 ... 24 more
Time[2009-01-28 02:02:33,039] [ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'::: TRACE javax.faces.webapp.FacesServlet - - Message[-service end]
Any idea why this error is coming? I see all the jar files in APP-INF/lib folder.

Hi fechen,
Could you please give your solution more detail?
Here is my weblogic.xml. The issue still exist.
<!DOCTYPE weblogic-web-app PUBLIC
"-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>-1</param-value>
</jsp-param>
</jsp-descriptor>
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2</implementation-version>
<exact-match>false</exact-match>
</library-ref>
<container-descriptor>
<servlet-reload-check-secs>-1</servlet-reload-check-secs>
<prefer-web-inf-classes>false</prefer-web-inf-classes>
</container-descriptor>
<context-root>/DataServices</context-root>
</weblogic-web-app>

The function "containsIgnoreCase" for prefix "fn" can not be found in the specified tag library.

Hi All,
I am getting this error on my jsff
The function "containsIgnoreCase" for prefix "fn" can not be found in the specified tag library.
jsff includes -
 <jsp:root xmlns:f="http://java.sun.com/jsf/core"
 xmlns:fn="http://java.sun.com/jsp/jstl/functions"
 xmlns:c="http://java.sun.com/jsp/jstl/core">
Error at this line - <af:inputListOfValues
 disabled="#{fn:containsIgnoreCase(bindings.Items.attributeValue,'XYZ')}" >
Is it Library file issue ? I have already added JSTL1.2.

Hi Frank,
I have imported the same directly by code.
I am facing this issue on one of my system, but the same code is working fine in my other systems. I have tried re-insatlling jdev and importing all the files.
But still facing the same issue.. This might be some jdev issue in specific system ?
Please let me know if anything i need to add .

Navigation Tag Library in Consumer Portal of Federated Portal Network

In a FPN scenario, is it possible to use the Navigation Tag Library in the consumer portal for the top level navigation? I have developed a custom top level navigation based on the navigation tag library, but when navigating to the role of the producer and back again I can no longer view the roles in the consumer portal.

Hi,
I know this was posted a long time ago, but I'm currently experiencing a similar issue in the TLN between a federated CE and EP portal. Did you manage to resolve your problem? In my case it looks like when you access the CE content from EP it cannot find its way back to EP when clicking on another link on the EP side. Looking at the logs it seems as if it's looking for the content on the CE system even though it's obviously not there.
Cheers,
Dion

BUG: Unable to add tag library to component palette on linux (Ubuntu)

As already discussed in the thread problem with adding Sun JSF RI v1.2 as a new library in JDeveloper 10.1.3.1 i have problems adding the Apache Trinidad (faces) tag library to the component palette. Actually the adding is not the problem and initially after adding it, it works. But when closing JDeveloper and restarting the components have disappeared while they are still selected in the Edit Tag Libraries menu. This problem only occurs on Linux and not under windows.
Kind Regards,
Andre Jochems

Hi,
Thanks for reporting this issue
Frank

Apache's Session Tag Library

Hi
 Has anyone had any success in using apache's session tag library
 (http://jakarta.apache.org/taglibs/doc/session-doc/intro.html) on WLS 5.1
 SP7. I have just set up the example as a web app and the server starts up
 with no problems. However, when I run it I get the following error:
 Tue Mar 06 13:29:29 GMT+00:00 2001: <WebAppServletContext-test> resolving
 tag
 lib uri 'http://jakarta.apache.org/taglibs/session-1.0' to taglib-location
 /WEB-
 INF/session.tld:
 Tue Mar 06 13:29:30 GMT+00:00 2001:<E> <WebAppServletContext-test> Servlet
 faile
 d with Exception
 weblogic.servlet.jsp.JspException: (line 22): ss is not defined as bean
 at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:665)
 at
 weblogic.servlet.jsp.JspLexer.mXML_GET_PROPERTY(JspLexer.java:2932)
 at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1650)
 at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1555)
 at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
 at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
 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:302)
 at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
 at
 weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.
 java:164)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
 pl.java:101)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
 pl.java:124)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
 textImpl.java:907)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
 textImpl.java:851)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
 ContextManager.java:252)
 at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
 a:364)
 at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 I am not sure if this is an error in their taglib implementation or whether
 it is a weblogic issue. Just thought I would ask if anyone else has had
 similar problems ???
 Cheers
 Lee
 Lee Turner
 Systems Developer
 Watt Gilchrist Ltd
 Ring Road, West Park
 Leeds, LS16 6RA
 Tel: 0113 288 3200
 Fax: 0113 275 1690
 http://www.wattgilchrist.co.uk


I think you should make sure you have put the Session bean object/remote interface into the session using setAttribute and have binded it with a key, if not you certainly cannot get it from session using getAttribute. right?

Connection Pooling and JSP Custom Tag Library - is code (inside) the best way/correc?

Hi, can anyone advise as to whether my tag library code (based
on Apache Jakarta Project) will actually achieve connection
pooling functionality across my entire JSP based application? I
am slightly concerned that my OracleConnectionCacheImpl object
may exist multiple times, hence rendering my conection pooling
attempt useless.
package com.solved.tag.dbtags.connection;
import java.io.IOException;
import java.sql.Connection;
import java.sql.SQLException;
import javax.servlet.jsp.tagext.TagSupport;
import javax.servlet.jsp.JspTagException;
import javax.sql.DataSource;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import oracle.jdbc.pool.OracleConnectionCacheImpl;
* JSP tag connection, used to get a
* java.sql.Connection object.
* JSP Tag Lib Descriptor
* <pre>
* <name>connection</name>
<tagclass>com.solved.tag.dbtags.connection.ConnectionTag</t
agclass>
* <bodycontent>JSP</bodycontent>
<teiclass>com.solved.tag.dbtags.connection.ConnectionTEI</t
eiclass>
* <info>Opens a connection based on a jndiName.</info>
* <attribute>
* <name>id</name>
* <required>true</required>
* <rtexprvalue>false</rtexprvalue>
* </attribute>
* </pre>
* @author Matt Shannon
public class ConnectionTag extends TagSupport {
static private OracleConnectionCacheImpl cache = null;
public int doStartTag() throws JspTagException {
try {
Connection conn = null;
if (cache == null) {
try {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup
("jdbc/pool/OracleCache");
cache = (OracleConnectionCacheImpl)ds;
catch (NamingException ne) {
throw new JspTagException(ne.toString());
conn = cache.getConnection();
pageContext.setAttribute(getId(),conn);
catch (SQLException e) {
throw new JspTagException(e.toString());
return EVAL_BODY_INCLUDE;
package com.solved.tag.dbtags.connection;
import java.sql.Connection;
import java.sql.SQLException;
import javax.servlet.jsp.tagext.TagSupport;
* JSP tag closeconnection, used to close the
* specified java.sql.Connection.
* JSP Tag Lib Descriptor
* <pre>
* <name>closeConnection</name>
<tagclass>com.solved.tag.dbtags.connection.CloseConnectionTag&
lt;/tagclass>
* <bodycontent>empty</bodycontent>
* <info>Close the specified connection. The "conn"
attribute is the name of a
* connection object in the page context.</info>
* <attribute>
* <name>conn</name>
* <required>true</required>
* <rtexprvalue>false</rtexprvalue>
* </attribute>
* </pre>
* @author Matt Shannon
* @see ConnectionTag
public class CloseConnectionTag extends TagSupport {
private String _connId = null;
* The "conn" attribute is the name of a
* page context object containing a
* java.sql.Connection.
* @param connectionId
* attribute name of the java.sql.Connection to
close.
* @see ConnectionTag
public void setConn(String connectionId) {
_connId = connectionId;
public int doStartTag() {
try {
Connection conn = (Connection)pageContext.getAttribute
(_connId);
conn.close();
} catch (SQLException e) {
// failing to close a connection is not fatal
e.printStackTrace();
return EVAL_BODY_INCLUDE;
public void release() {
_connId = null;
package com.solved.tag.dbtags.connection;
import javax.servlet.jsp.tagext.TagData;
import javax.servlet.jsp.tagext.TagExtraInfo;
import javax.servlet.jsp.tagext.VariableInfo;
* TagExtraInfo for the connection tag. This
* TagExtraInfo specifies that the ConnectionTag
* assigns a java.sql.Connection object to the
* "id" attribute at the end tag.
* @author Matt Shannon
* @see ConnectionTag
public class ConnectionTEI extends TagExtraInfo {
public final VariableInfo[] getVariableInfo(TagData data)
return new VariableInfo[]
new VariableInfo(
data.getAttributeString("id"),
"java.sql.Connection",
true,
VariableInfo.AT_END
data-sources.xml:
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "Orion data-
sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
<data-source
class="oracle.jdbc.pool.OracleConnectionCacheImpl"
name="jdbc/pool/OracleCache"
location="jdbc/pool/OracleCache"
url="jdbc:oracle:thin:@oracle1:1521:pdev"
>
<property name="maxLimit" value="15" />
<property name="cacheScheme" value="2" />
<property name="user" value="console" />
<property name="password" value="console" />
<description>
This DataSource is using an Oracle-native DataSource Class so as
to allow Oracle Specific extensions.
A getConnection() call on this DataSource will return
oracle.jdbc.driver.OracleConnection.
The connection returned is a logical connection.
The caching scheme in place is Fixed Wait. Refer below to
possible values.
Dynamic 1
Fixed Wait 2
Fixed Return Null 3
</description>
</data-source>
</data-sources>
many thanks,
Matt.

Hi. Show me your pool definition.
Joe
Ramamurthy wrote:
I am using the jsp custom tag library from BEA called sqltags.tld which came with Weblogic 5.1. Currently I am using Weblogic6.1 sp2 on Solaris.
I have created a Connection Pool for Sybase database using the driver com.sybase.jdbc.SybDriver.
When I created jsp page to connect to the connection pool using sqltags custom tag library, I am getting the error
"javax.servlet.jsp.JspException: Failed to write body content
at weblogic.taglib.sql.ConnectionTag.doAfterBody(ConnectionTag.java:43)
at jsp_servlet.__hubwcdata._jspService(__sampletest.java:1014)"
After this message, whenever I try to access the same jsp page I am getting the message
"javax.servlet.jsp.JspException: Failed to load JDBC driver: weblogic.jdbc.pool.D
river
at weblogic.taglib.sql.ConnectionTag.doStartTag(ConnectionTag.java:34)
at jsp_servlet.__hubwcdata._jspService(__sampletest.java:205)".
Can you please help me the reason why this problem is happening and how to fix this ?
This problem doexn't happen consistently. This occurs once in a while.
I tried to increase Login delay Seconds parameter in the Connection Pool to 15 sec. It didn't help me much.
Thanks for your help !!!
Ram

Tag library issue

Similar Messages

Maybe you are looking for