Error in tld file

Hi,
I'm getting the below mentioned error in my tld file
cvc-complex-type.2.4.b: The content of element 'tag' is not complete. One of '{"http://java.sun.com/xml/ns/javaee":tei-class, "http://java.sun.com/
xml/ns/javaee":body-content}' is expected.
tld file :
<taglib xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd"
version="2.1">
     <tlib-version>1.0</tlib-version>
     <short-name>privilager</short-name>
     <uri>http://tags/privilager</uri>
     <tag>
     <name>check</name>
     <tag-class>com.boss.jstl.Privilager</tag-class>
     </tag>
</taglib>
Kindly help me to solve this issue.
Thanks in advance

Similar Messages

Error in parsing taglib 'customtag' tag in web.xml or .tld file of the tagl

Hi
While execution Portal application, I am getting error," Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library."
Complete stack is
>>#1.5 #005056AE006400690000002000000A440004BA8F3ECB004A#1331024303056#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#M1005000#6994##99593FD6676911E1807500000041A352#99593fd6676911e1807500000041a352-0#99593fd6676911e1807500000041a352#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###02:28_06/03/12_0020_4301650
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException: Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library.
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:189)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse0(JspDirective.java:162)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse(JspDirective.java:117)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ElementCollection.parse(ElementCollection.java:86)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ParserImpl.parse(ParserImpl.java:595)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2170)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:133)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Regards
Pratyush

Hi,
See the following guide and make sure to carefully follow all instructions.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40599e45-8cf9-2910-cbaa-d4cd8e15ff34?QuickLink=index&overridelayout=true&14770392545262]
Regards,
Alex

Error in parsing taglib taglib tag in web.xml or .tld file of the taglib

Hi All,
I have added ResourceBundle.tld file in following path : /PORTAL-INF/taglib/tld/
I have added portalapp.xml file following entry :
<property name="/PORTAL-INF/taglib/tld/ResourceBundle.tld" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
I have added jsp file following entry :
<%@ taglib uri="/PORTAL-INF/taglib/tld/ResourceBundle.tld" prefix="bundle" %>
I am getting the following the error: Error in parsing taglib taglib tag in web.xml or .tld file of the taglib library
can you tell me where i am giving the wrong.
Regards
Siva

hi rabih,
in jsp..
<%@ taglib uri="tagLib" prefix="bundle" %>
in portalapp.xml
<component-profile>
<property name="tagLib" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
</component-profile>
it may help u..
regards,
Chinnadurai.R

Can't figure out what this error means for a TLD file

I am new to Java and I am getting the following error. I a tld file in a tlds folder under the Web-inf folder. I am running tomcat 5.5.17. I also put the file in the Web.xml. What else do I need to do?
javax.servlet.ServletException: javax.servlet.jsp.tagext.TagInfo.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljavax/servlet/jsp/tagext/TagLibraryInfo;Ljavax/servlet/jsp/tagext/TagExtraInfo;[Ljavax/servlet/jsp/tagext/TagAttributeInfo;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljavax/servlet/jsp/tagext/TagVariableInfo;Z)V
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:272)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
root cause
java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagInfo.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljavax/servlet/jsp/tagext/TagLibraryInfo;Ljavax/servlet/jsp/tagext/TagExtraInfo;[Ljavax/servlet/jsp/tagext/TagAttributeInfo;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljavax/servlet/jsp/tagext/TagVariableInfo;Z)V
     org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java:435)
     org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:248)
     org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:162)
     org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:423)
     org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1552)
     org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
     org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

Using Java 1.5. This code is from a book example, and I tried emailing the company, but haven't heard anything.
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
<taglib>
<tlibversion>1.0</tlibversion>
<jspversion>1.2</jspversion>
<shortname></shortname>
<info>The tag library for the murach applications</info>
<tag>
<name>today</name>
<tagclass>tags.SimpleDateTag</tagclass>
<info>Returns the current date</info>
</tag>
<tag>
<name>time</name>
<tagclass>tags.CurrentTimeTag</tagclass>
</tag>
<tag>
<name>checkfield</name>
<tagclass>tags.AttributeRequiredTag</tagclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>color</name>
<required>false</required>
</attribute>
<attribute>
<name>field</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
</tag>
<tag>
<name>weekday</name>
<tagclass>tags.BodyWeekdayTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>products</name>
<tagclass>tags.ProductsTag</tagclass>
<teiclass>tags.ProductsTEI</teiclass>
<bodycontent>JSP</bodycontent>
</tag>
</taglib>
This is the SimpleDateTag class, which is being referenced.
package tags;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import java.io.*;
import java.util.*;
import java.text.DateFormat;
public class SimpleDateTag extends TagSupport{
public int doStartTag() throws JspException{
Calendar calDate = new GregorianCalendar();
Date now = calDate.getTime();
DateFormat shortDate = DateFormat.getDateInstance(DateFormat.SHORT);
String today = shortDate.format(now);
try {
JspWriter out = pageContext.getOut();
out.print("The current date is " + today + ".");
catch (IOException ioe){
System.out.println("SimpleDateTag IOException: " + ioe);
return SKIP_BODY;
}

How to use tld files in iPlanet

Hai Friends,
I don't know basic stuff of iPlanet. plz help me. I have developed one application in tomcat. Now i need to move that application from tomcat to iPlanet 6.0(Solaris). When i deployed it in iPlanet i am geting following exceptions plz guide me
[02/May/2006:17:40:18] failure (26802): Internal error: servlet service function had thrown ServletException (uri=/ACM/jsp/bottom_pa
ge1.jsp): org.apache.jasper.compiler.ParseException: /user3/acm/iplanet/servers/ACM/jsp/bottom_page1.jsp(2,0) Page directive: Invali
d attribute, pageEncoding, stack: org.apache.jasper.compiler.ParseException: /user3/acm/iplanet/servers/ACM/jsp/bottom_page1.jsp(2,0
) Page directive: Invalid attribute, pageEncoding
at org.apache.jasper.compiler.JspUtil.checkAttributes(JspUtil.java:237)
at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:194)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1077)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1042)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1038)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:218)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadJSP(JspServlet.java:193)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$4(JspServlet.java:167)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:477)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:897)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
, root cause:
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element tag-class in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element body-content in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element tag-class in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element body-content in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] info (26802): JSP11 Log:Warning: Unknown element variable in tag
[02/May/2006:17:40:18] failure (26802): Internal error: servlet service function had thrown ServletException (uri=/ACM/jsp/header.js
p): org.apache.jasper.compiler.CompileException: /user3/acm/iplanet/servers/ACM/jsp/header.jsp(101,0) Unable to load class null, sta
ck: org.apache.jasper.compiler.CompileException: /user3/acm/iplanet/servers/ACM/jsp/header.jsp(101,0) Unable to load class null
at org.apache.jasper.compiler.TagBeginGenerator.init(TagBeginGenerator.java:128)
at org.apache.jasper.compiler.JspParseEventListener$GeneratorWrapper.init(JspParseEventListener.java:753)
at org.apache.jasper.compiler.JspParseEventListener.addGenerator(JspParseEventListener.java:132)
at org.apache.jasper.compiler.JspParseEventListener.handleTagBegin(JspParseEventListener.java:903)
at org.apache.jasper.compiler.DelegatingListener.handleTagBegin(DelegatingListener.java:188)
at org.apache.jasper.compiler.Parser$Tag.accept(Parser.java:825)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1077)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1042)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1038)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:218)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadJSP(JspServlet.java:193)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$4(JspServlet.java:167)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:477)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:897)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
, root cause:
(END)

Thank u Very much.
And small doubt again. I am writing one custom tag in my application for that we need one tld file. In tomcat i wrote like this
<tag>
<name>Menu</name>
<tag-class>com.citigroup.acm.taglib.MenuTag</tag-class>
<body-content>JSP</body-content>
<variable><name-given>parentId</name-given></variable>
</tag>
but in iPlanet i modified(insted of tag-class i used tagclass) like the following, b'coz i got some exceptions
<tag>
<name>Menu</name>
<tagclass>com.citigroup.acm.taglib.MenuTag</tagclass>
<body-content>JSP</body-content>
<variable><name-given>parentId</name-given></variable>
</tag>
Now i am getting error at <variable> how to handle that plz help me

How to install the struts-el jar and tld file

How can i install/configure the struts-el jar and struts-logic-el.tld. When I tried with the related sites, i couldn't get any jar files for struts-el tag.
I got only 404 status error.
From where and how to get the jar file and tld file for the struts-el tag .Please refer me

The jar file is part of the download of struts.
its in the /contrib/lib directory
You should need struts, jstl plus the struts-el jar files.
The tld files should not be necessary - just use the standard URIs for them.
eg http://struts.apache.org/tags-logic-el

How to configure tld file?

I am building a JSF application and created a new custom component with a new tag. I suspect the runtime isn't finding/loading my TLD file. I've tried putting the TLD file in the WEB-INF directory and with the source/class files; I get the same error. How can I figure out if my tld is loaded? what else can I try to get it to be recognzied properly?
The error is:
Attribute id invalid for tag TestTag according to TLDMy TLD file does specify id:
          <attribute>
               <name>id</name>
               <required>false</required>
               <rtexprvalue>false</rtexprvalue>
               <description>
                    The component identifier for this component. This value
                    must be unique within the closest parent component that
                    is a naming container.
               </description>
          </attribute>

If I flat out delete the tld file, and restart my IDE and the web server, I get the exact same symptoms. My custom tag/component works perfectly with a value attribute but no id attribute. As soon as I add the id attribute, I get the error.
I can also put the tld file back, but delete the XML contents and type in garbage; this way, if something was trying to read that file it would error. I get no error, which tells me that nothing is reading that file. If I remove the id attribute, it works perfectly.
My import statement:
<%@ taglib uri="http://sample.com/taglibs/" prefix="xyz"%>My tag reference:
<td><xyz:rater value="#{sample.value}" /></td>Java: 1.5.0_06
Server: Apache Tomcat 5.5.12
JSF: Sun RI 1.1_01
IDE: Eclipse 3.1.1 + WTP 1.0RC5
Yes, in my web searches, I saw many places recommending adding a taglib section to web.xml, but it wouldn't validate and seemed to be obsolete.

How to make reference to ENTITY in tld file ?

Hello,
I have a tld file in which in put the definition of my own components.
I'd like to create ENTITY in XML and make reference to those entities in this tld, in order to make the tld smaller.
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
"http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd" [
<!ENTITY display_value_only_attributes SYSTEM "entities/display_value_only_attributes.xml">
]>
&display_value_only_attributes;But when I make this, I got the following exception:
2007-02-05 11:46:57,881 ERROR [org.apache.catalina.startup.TldConfig] Exception processing TLD META-INF/cwsoft.tld in JAR at resource path C:\jboss-4.0.1sp1\server\default\tmp\deploy\tmp28432cwsoft-technicalframework-web-1.2.2-exp.war\WEB-INF\lib\cwsoft-cweb-1.2.2.jar in context /cwsoft/technicalframework
java.io.FileNotFoundException: C:\jboss-4.0.1sp1\bin\entities\display_value_only_attributes.xml
     at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
     at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
     at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
     at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
     at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at org.apache.commons.digester.Digester.parse(Digester.java:1647)
     at org.apache.catalina.startup.TldConfig.tldScanStream(TldConfig.java:514)
     at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:472)
     at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:307)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4282)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
     at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.apache.catalina.core.StandardContext.init(StandardContext.java:5441)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
     at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:289)
     at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:92)
     at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:374)
     at org.jboss.web.WebModule.startModule(WebModule.java:62)
     at org.jboss.web.WebModule.startService(WebModule.java:40)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:418)
     at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy24.start(Unknown Source)
     at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:360)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy8.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:418)
     at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy4.start(Unknown Source)
     at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy5.deploy(Unknown Source)
     at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
     at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
     at org.jboss.Main.boot(Main.java:195)
     at org.jboss.Main$1.run(Main.java:463)
     at java.lang.Thread.run(Thread.java:534)Could someone indicates me how to make it work?
Thanks in advance.
bgOnline

No, indeed !
But I forgot to specify that this file is placed in my jar that is included is my war.
So, I'd like to make reference to this file, and not to put it somewhere in my AS.
Thanks for your reply...

JspParseException: TLD file under JAR's META-INF not found

I have succesully deployed an external generated WAR file using the Developer Studio 'Deploy View'. However, I get an exception at runtime:
com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [http://www.some.url/some/location].
This URI is defined in a TLD file which is embeded in the META-INF of a JAR which is located in WEB-INF/lib of the WAR file.
This same exact WAR file deploys fine in Tomcat.
Could this be a bug in the J2EE Preview? Any workarounds here?
Enrique

Hello everybody
I,ve the same problem when I try to deploy a jsf application that uses Esri tags.
The war work fine In a Tomcat but when I deploy the application in the WAS 5 I get the error Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [http://www.esri.com/adf/web].
I think there aren't problems with the TLD because the proyect runs fine in other environment. It seems like the WAS wasn't able to connect with the URI.
Do you know any solution ?
Thank in advance.
Fernando

Why can't TLD files be shared?

First, a disclaimer: I'm an absolute newbie to JSP programming, so I may easily be overlooking something. If so, please point me in the right direction. :)
Second, a complaint (and I have a hard time believing that I'm the only one that's ever had this problem): why can't TLD files be shared between applications?
Where I work (at a university) we don't write single, stand-alone "applications"; we write "systems." A single system consists of multiple interdependent application, each of which may share aspects of their presentation with (potentially) many other applications.
Sure, I could put the tag library definition files in the WEB-INF directories of each of these applications. Then, each application can access the tags no problem, right? Right.
However, what happens when one of those tags is updated, or a new tag is created? I suddenly need to redeploy many (possibly more than 100) applications, just so that I can update the silly little TLD file in the WEB-INF directory of each of those WAR files.
Am I the only one that feels (strongly) that this is a major flaw in the design of JSP? Is there some obvious way to share these files that I am overlooking? Any help would be very welcome, but frankly, this is really discouraging me. For all the talk of JSP promoting component reuse, this one issue seems like a major argument in the other direction...
- Jamis Buck

Hi Jamis
According to JSP Spec :
The TLD resource path is interpreted relative to the root of the web
application and should resolve to a TLD file directly, or to a JAR file that has a
TLD file at location META-INF/taglib.tld. If the TLD resource path is not one of
these two cases, a fatal translation error will occur.
It must be possible to share the tld file as long as it is possible to share a jar file ;)
I will provide you with more information and example later.

Location of .tld file

Hi all,
I am a novice user. I have made a class file, a .tld file and a .jsp file. I tried to run them on JDeveloper 10g. Class n .tld file ran fine. But when i ran .jsp it gave me two errors...
Error(3): java.io.FileNotFoundException: C:\jdev1012\jdev\mywork\JSP1\JSP11\public_html\WEB-INF\mytags.tld (The system cannot find the file specified)
Error(3): Unable to load taghandler class: WEB-INF/mytags.tld
Can anybody help me. I think its the location of the tag discriptor file.
Mansih Dani
Student
Kingston University, London
[email protected]

To the web.xml add
<taglib>
<taglib-uri>/WEB-INF/mytags.tld</taglib-uri>
<taglib-location>/WEB-INF/mytags.tld</taglib-location>
</taglib>

Error parsing TLD?!

Hi everyone:
I test my taglib file use JRun.I place the .tld and the .class in correct dir.But when I compile my jsp file testtag.jsp and JRun report the under error:
////////////////////////testtag.jsp/////////////
Error parsing TLD '/WEB-INF/taglib/mytag.tld': com.sun.xml.parser/P-082 http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd.
org.xml.sax.SAXParseException: com.sun.xml.parser/P-082 http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd
     at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
     at com.sun.xml.parser.Parser.externalParameterEntity(Parser.java:2506)
     at com.sun.xml.parser.Parser.maybeDoctypeDecl(Parser.java:1137)
     at com.sun.xml.parser.Parser.parseInternal(Parser.java:481)
     at com.sun.xml.parser.Parser.parse(Parser.java:284)
     at com.sun.xml.parser.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:95)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:78)
     at allaire.jrun.jsp.JRunTagLibraryInfo.<init>(../jsp/JRunTagLibraryInfo.java:198)
     at allaire.jrun.jsp.JRunTagLibraryInfo.lookupTLI(../jsp/JRunTagLibraryInfo.java:109)
     at allaire.jrun.jsp.JSPParser.taglibDirective(../jsp/JSPParser.java:842)
     at allaire.jrun.jsp.JSPParser.directive(../jsp/JSPParser.java:973)
     at allaire.jrun.jsp.JSPParser.parse(../jsp/JSPParser.java:921)
It seems the .dtd problem.But I download the .dtd1.2 for my JRun and the problem remain happen! What does it mean?Could anyone explanation for me?

Hi tolmank:
Thank you to reply.I open it with xmlwriter.It report error when I run it.It says:
DTD can't have DTD declare in external DTD��handle source: 'file:///E:/JRun/lib/web-jsptaglibrary_1_2.dtd' a error happen��nineteen range��location: 12
<!NOTATION WEB-JSPTAGLIB.1_2 PUBLIC "-//Sun Microsystems, Inc.//DTD JSP T... .
-----------^
But I download the DTD file from sun's homepage!Why?

Error in TLD(jsp custom tags)

Hi frinend
iam trying jsp custom tabs (taglibs)
i worte a java class
i worte a jsp page
i worte a TLd file
the proble with tlb
it geting error like this
org.apache.jasper.JasperException: XML parsing error on file /WEB-INF/jsp/mytaglib.tld: (line 2, col -1): XML declaration may only begin entities.
what is that mean
i wrote in tld file like this
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd ">

<taglib>
<tlibversion>1.0</tlibversion>
<jspversion>1.1</jspversion>
<shortname>first</shortname>
<uri></uri>
<info>A simple tab library for the
examples</info>
<tag>
<name>hello</name>
<tagclass>tags.HelloTag</tagclass>
<bodycontent>empty</bodycontent>
<info>Say Hi</info>
</tag>
</taglib>
pls help
regards
kedar

try something that looks like this in your 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>
<tlib-version>1.2</tlib-version>
<jsp-version>1.2</jsp-version>
<short-name>MyFirstTag</short-name>
<tag>
<name>helloparam</name>
<tag-class>tags.HyperTag</tag-class>
<body-content>empty</body-content>
<attribute>
<name>name</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
</tag>
</taglib>

Is tld file necessary?

Dear dudes,
I was working with JSTL , in which i'm using pre-defined tag libraries which contains many functionalities which is defined in TLD files. For example:
*<%@ taglib uri="WEB-INF/tld/struts-html" prefix="html" %>*Here this means i can use the html tags functionality which is defined in the uri i.e. tld files which defines the class and functionality.
here if i use some X() functionality in html tags, the container goes through the tld files and finds the corresponding method or function.
Why this should be like this?
<%@ taglib uri="WEB-INF\*lib\struts.jar*" prefix="html" %>
Why can't i directly refer the location of resource ( here the jar file) to the container so that these intermediate tld file mapping can be skipped.
Why is the tld file significant?
Any valid reply would be appreciated.
regards.

nammathamizhan wrote:
Dear dudes,
I was working with JSTL , in which i'm using pre-defined tag libraries which contains many functionalities which is defined in TLD files. For example:
*<%@ taglib uri="WEB-INF/tld/struts-html" prefix="html" %>*Here this means i can use the html tags functionality which is defined in the uri i.e. tld files which defines the class and functionality.
here if i use some X() functionality in html tags, the container goes through the tld files and finds the corresponding method or function.
Why this should be like this?
<%@ taglib uri="WEB-INF\*lib\struts.jar*" prefix="html" %>
Why can't i directly refer the location of resource ( here the jar file) to the container so that these intermediate tld file mapping can be skipped.
Why is the tld file significant?
Any valid reply would be appreciated.
regards.If i understand your question clearly, you mean to ask why not declare the <%@ taglib uri....%> in the .jsp file rather than the web.xml file right?
The simple reason for this is that we delcare the .jar files in the lib folder, which we reference in the web.xml file. The container reads the web.xml file first before reading your .jsp files. So if the mapping is not mentioned in the web.xml file you get an error. This is the working of the container, every mapping, filter, custom tag et all should be mentioned in the web.xml file(also called a deployment descriptor file). Read more about the deployment descriptor or web.xml in the docs.

Auto-discovery for TLD files in WEB-INF

The auto-discovery mechanism in JSP 1.2 can scan through the WEB-INF directory structure for files with .tld exntension and find all <uri> definitions in them, so we can use a symbolic name to map to the actual location of the tld file by using:
<%@ taglib prefix="test" uri="mytaglib" %>
in a JSP page.
My colleague and I did not have luck in making this work. I got the following error message:
"500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib prefix="test" uri="kltaglib" %>
Error: java.io.FileNotFoundException: C:\oc4j\j2ee\home\applications\myapp\myapp-web\mytaglib (The system cannot find the file specified) "
The symbolic name was not recognized. Is this a limitation in OC4J? Has anyone make this work? However, another way of auto-discovery by META-INF in JAR files works for me.
Thanks.

The auto-discovery mechanism in JSP 1.2 can scan through the WEB-INF directory structure for files with .tld exntension and find all <uri> definitions in them, so we can use a symbolic name to map to the actual location of the tld file by using:
<%@ taglib prefix="test" uri="mytaglib" %>
in a JSP page.
My colleague and I did not have luck in making this work. I got the following error message:
"500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib prefix="test" uri="kltaglib" %>
Error: java.io.FileNotFoundException: C:\oc4j\j2ee\home\applications\myapp\myapp-web\mytaglib (The system cannot find the file specified) "
The symbolic name was not recognized. Is this a limitation in OC4J? Has anyone make this work? However, another way of auto-discovery by META-INF in JAR files works for me.
Thanks.

Error in tld file

Similar Messages

Maybe you are looking for