Taglib URI

Hi
I'm developing portlets with JAVA EE 5, Tomcat 5.5.x and Spring Framework 2.0.
JSP + JSTL are used for views.
In my jsp pages I have a line
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
which work fine and I can use the core taglib and its tags.
However, if I read the Java EE 5 manual at http://java.sun.com/javaee/5/docs/tutorial/doc/JSPIntro9.html#wp73319 (at the end) it says that:
The absolute URIs for the JSTL library are as follows:
* Core: http://java.sun.com/jsp/jstl/core
This URI doesn't work for me. Is this a problem with Tomcat 5.5.9 or am I using wrong jar somewhere? I think jstl.jar is the one to look for - which version should I use and how do I know which version I have?
Error:
Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /WEB-INF/jsp/index.jsp(1,1) The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
with best regards Fredrik

The difference is between JSTL1.0 and JSTL1.1
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %> = JSTL1.0
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/jsp/core" %> = JSTL1.1
You can check the version by looking at the file Manifest.mf in the META-INF file of standard.jar or jstl.jar
You most probably have JSTL1.0 installed.

Similar Messages

  • Error in using taglib uri in jsp

    When i write the following code in my jsp to use the tags, i got the error -
    JSP Parsing Error:The absolute uri: http://java.sun.com/jsf/html cannot be resolved in either web.xml or the jar files deployed with this application     
    And when i used the tld (html_basic.tld & jsf_core.tld), it gave me the error
    JSP Parsing Error:Failed to load or instantiate TagLibraryValidator class: com.sun.faces.taglib.html_basic.HtmlBasicValidator

    you can use
    <taglib>
    <taglib-uri>/WEB-INF/html-basic.tld</taglib-uri>
    <taglib-location>
    /WEB-INF/html-basic.tld
    </taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/jsf-core.tld</taglib-uri>
    <taglib-location>
    /WEB-INF/jsf-core.tld
    </taglib-location>
    </taglib>
    in your web.xml

  • Taglib URI error in Weblogic60

    Hi All,
              having some trouble deploying my custom Tag, this is the error...
              thanks in advance
              Parsing of JSP File '/test/tagpage.jsp' failed:
              /test/tagpage.jsp(1): Could not parse deployment descriptor:
              java.io.IOException: cannot resolve 'taglib' into a valid tag library
              probably occurred due to an error in /test/tagpage.jsp line 1:
              <%@ taglib uri="taglib" prefix="input" %>
              my directories look like this
              myserver
              test
              - tagpage.jsp
              WEB-INF
              -web.xml
              -taglib.tld
              my code:
              in jsp
              -<%@ taglib uri="taglib" prefix="input" %>
              in web.xml
              -<?xml version="1.0" ?>
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
              1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              <web-app>
              <taglib>
              <taglib-uri>taglib</taglib-uri>
              <taglib-location>/WEB-INF/taglib.tld</taglib-location>
              </taglib>
              </web-app>
              

    I get the following error when I try to get my taglibs running in WLS 6.0 -
              any ideas?
              Parsing of JSP File '/Project.jsp' failed:
              /Project.jsp(3): Could not parse deployment descriptor:
              org.xml.sax.SAXParseException: Could not parse: taglib starting at line 1
              probably occurred due to an error in /Project.jsp line 3:
              <%@ taglib prefix="rdbm" uri="/rdbmstags6_0.tld" %>
              Tue Feb 20 10:41:57 MST 2001
              "Mark S." <[email protected]> wrote in message
              news:[email protected]...
              > Hi All,
              >
              > having some trouble deploying my custom Tag, this is the error...
              >
              > thanks in advance
              >
              > Parsing of JSP File '/test/tagpage.jsp' failed:
              >
              > /test/tagpage.jsp(1): Could not parse deployment descriptor:
              > java.io.IOException: cannot resolve 'taglib' into a valid tag library
              > probably occurred due to an error in /test/tagpage.jsp line 1:
              > <%@ taglib uri="taglib" prefix="input" %>
              >
              > ------------------------------
              >
              > my directories look like this
              >
              > myserver
              >
              > test
              >
              > - tagpage.jsp
              >
              > WEB-INF
              >
              > -web.xml
              >
              > -taglib.tld
              >
              > -------------------------------
              >
              > my code:
              >
              > in jsp
              >
              > -<%@ taglib uri="taglib" prefix="input" %>
              >
              > in web.xml
              >
              > -<?xml version="1.0" ?>
              >
              > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
              > 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              >
              > <web-app>
              >
              > <taglib>
              >
              > <taglib-uri>taglib</taglib-uri>
              >
              > <taglib-location>/WEB-INF/taglib.tld</taglib-location>
              >
              > </taglib>
              >
              > </web-app>
              >
              >
              >
              

  • Taglib uri problem

    Hi all
    I created a web module project and add a JSP file u201CcustomTagWelcome.jspu201D and a TLD file u201Cadvjhtp1-taglib.tldu201D to the webContent directory. I added also a tag handler
    u201CWelcomeTagHandleru201D.
    The jsp code:
    <?xml version = "1.0"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <!-- Fig. 10.30: customTagWelcome.jsp               -->
    <!-- JSP that uses a custom tag to output content. -->
    <%-- taglib directive --%>
    <%@ taglib uri = "advjhtp1-taglib.tld" prefix = "advjhtp1" %>
    <html xmlns = "http://www.w3.org/1999/xhtml">
       <head>
          <title>Simple Custom Tag Example</title>
       </head>
       <body>
          <p>The following text demonstrates a custom tag:</p>
          <h1>
             <advjhtp1:welcome />
          </h1>
       </body>
    </html>
    The tld content:
    <?xml version = "1.0"?>
    <!DOCTYPE taglib PUBLIC
       "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
          "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
    <!-- a tag library descriptor -->
    <taglib>
       <tlibversion>1.0</tlibversion>
       <jspversion>1.1</jspversion>
       <shortname>advjhtp1</shortname>
       <info>
          A simple tab library for the examples
       </info>
       <!-- A simple tag that outputs content -->
       <tag>
          <name>welcome</name>
          <tagclass>
             com.deitel.advjhtp1.jsp.taglibrary.WelcomeTagHandler
          </tagclass>
          <bodycontent>empty</bodycontent>
          <info>
             Inserts content welcoming user to tag libraries
          </info>
       </tag>
       <!-- A tag with an attribute -->
       <tag>
          <name>welcome2</name>
          <tagclass>
             com.deitel.advjhtp1.jsp.taglibrary.Welcome2TagHandler
          </tagclass>
          <bodycontent>empty</bodycontent>
          <info>
             Inserts content welcoming user to tag libraries. Uses
             attribute "name" to insert the user's name.
          </info>
          <attribute>
             <name>firstName</name>
             <required>true</required>
             <rtexprvalue>true</rtexprvalue>
          </attribute>
       </tag>
       <!-- A tag that iterates over an ArrayList of GuestBean -->
       <!-- objects, so they can be output in a JSP            -->
       <tag>
          <name>guestlist</name>
          <tagclass>
             com.deitel.advjhtp1.jsp.taglibrary.GuestBookTag
          </tagclass>
          <teiclass>
             com.deitel.advjhtp1.jsp.taglibrary.GuestBookTagExtraInfo
          </teiclass>
          <bodycontent>JSP</bodycontent>
          <info>
             Iterates over a list of GuestBean objects
          </info>
       </tag>
    </taglib>
    In the u201Cothersu201D tab of web.xml I choose the tag-libs and for Taglib Location I choose the advjhtp1-taglib.tld. The Taglib Location is advjhtp1-taglib.tld. I added u201Cadvjhtp1-taglib.tldu201D as URI .  
    When I run the jsp in browser
    http://devsrv:50000/servlet_jsp/customTagWelcome.jsp
    I get the following exception:
    #1.5 #0019DB661008005B0000008A000013B000044FA2C2FDE9C9#1213460381553#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/servlet_jsp_test#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#Guest#0####b16b6e103a2d11ddb85a0019db661008#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Plain###application [servlet_jsp] Runtime error in compiling of the JSP file <C:/usr/sap/EP7/JC00/j2ee/cluster/server0/apps/sap.com/servlet_jsp_test/servlet_jsp/servlet_jsp/root/customTagWelcome.jsp> !
    The error is: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Tag library descriptor cannot be found for uri:].
    Exception id: [0019DB661008005B00000088000013B000044FA2C2FDE89A]#
    #1.5 #0019DB661008005B0000008B000013B000044FA2C2FDEBF1#1213460381553#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/servlet_jsp_test#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#0####b16b6e103a2d11ddb85a0019db661008#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###application [servlet_jsp] Processing HTTP request to servlet [jsp] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [C:/usr/sap/EP7/JC00/j2ee/cluster/server0/apps/sap.com/servlet_jsp_test/servlet_jsp/servlet_jsp/root/customTagWelcome.jsp].
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:118)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:429)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Tag library descriptor cannot be found for uri:].
         at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:146)
         at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse0(JspDirective.java:141)
         at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse(JspDirective.java:102)
         at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ElementCollection.parse(ElementCollection.java:89)
         at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ParserImpl.parse(ParserImpl.java:536)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:340)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:106)
         ... 18 more
    What is wrong with URI?
    Thanks in advance
    Yoel

    Hi,
    You need to add an entry for the <taglib-location> and <taglib-uri>
    in the web.xml for using a tld in the project.
    And then need to use the same url name in the jsp.
    You can go through the following link for the details about web.xml:
    http://edocs.bea.com/wls/docs61/webapp/web_xml.html#1017621
    Thanks
    Ritushree

  • What is the use of %@ taglib uri="taglib" prefix="hbj" % in jsp?

    what is the use of
    <%@ taglib uri="taglib" prefix="hbj" %>
    in jsp?
    The portal Content works fine even without that.
    Any specific reasons?

    Hello Hanif,
    This is the we declare taglibs in JSP files. Check this for definition:
    http://java.sun.com/products/jsp/tutorial/TagLibraries5.html#61992
    After declaring this taglib <%@ taglib uri="taglib" prefix="<b>hbj</b>" %>
    , you can use all HTMLB classes as tags in JSP.
    I am not sure in which JSP you mean that every thing works fine with out this taglib!! But if you remove this taglib, then you cannot use HTMLB in this JSP.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/42/efdb279a563ee7e10000000a1553f7/frameset.htm
    Greetings,
    Praveen Gudapati
    p.s Points are always welcome for helpful answers

  • How does the JSP container resolve taglib URI

    My application uses JSPs which have taglibs. The taglibs use absolute URIs(http://java.sun.com/jstl/core). I noticed that if the JAR which would resolve this taglib, which is standard.jar, were to be placed in the <domain>/lib folder, the application would not be able to resolve it. If i packaged the JAR with the taglib definitions in the WEB-INF/lib folder of the WAR file, the application worked fine. Any clues on if this is expected behaviour? I have some other taglibs which refer to http://java.sun.com/jsf/html and jsf/core - these seem to be resolved fine by placing the jsf-impl.jar in the <domain>/lib folder.
              Thanks
              Ramdas

    hello,
    unfortunatly it is not quite clear what type of security you want to achieve ...
    a) either securing the report for unauthorized running against different data
    or
    b) securing the stream between the server and the client using HTPPS
    for case a) you will have to code the logic into the report so a user can only run the report against his data.
    neither HTTPS nor the CGICMD.DAT can help you in this case. you could even use the row-level-security option of the database to achieve that.
    regards,
    the oracle reports team

  • When to specify taglib uri in web.xml

    When declaring a URI in the taglib directive, when must you include the taglib elements in web.xml, and when can you avoid them?
    I tried putting a relative path to the .tld file, setting uri to �/WEB-INF/mysubfolder/myfile.tld�, but my web server complains that I�m missing a tlib-version element somewhere�
    What is the uri path relative to, and in what cases must you include a mapping in web.xml and when do you not have to?
    Thanks.

    So it sounds like your tld file has some invalid xml in it.
    Double check the contents of your tld file.
    If you declare a <uri> in your taglibrary, then you never need to declare it in web.xml.
    You can just use that "well-known" uri to access your tag library.
    The tld has to be either
    1 - in the META-INF folder of a jar file deployed
    2 - under the WEB-INF directory
    See JSP specification section JSP.7.3.1

  • Taglib - uri Error

    Hi,
    when I compile a JSP with this fisrt statement:
    <%@ taglib prefix="foo" uri="/dir1/exampletag.tld" %>
    the JDeveloper (v3.2) show the error:
    "Start of root element expected".
    Please, how can I resolve it?...
    In my proyect:
    My "HTML root directory" is:
    C:\test\Html
    and the "HTML source directory" is:
    dir1
    The file "exampletag.tld" is in:
    C:\test\Html\dir1\exampletag.tld
    Thank you very much.
    Andres

    Thanks for the answers, but it has not still worked.
    I proved my tld file with a IE5 and it was read as an XML file without problem.
    The classes that are used in the tld file are also compiled. I use now a only one directory as a source, rundebug, output and html proyect's path in order to find the file easily, but without success.
    The examples that use DataTags.tld did not work neither. I read that a datatags "taglib jar file" must be added in the library proyect. Do you know the name of this jar file? There are many in the JDeveloper directory.
    Thanks for any comment...
    Andres
    null

  • JSP parse error "No URI for taglib" when using tagdir attribute

    Hi,
              I'm trying to use Jakarta JSTL 1.0 with BEA WebLogic 8.1 so I can work with tag files. I've put the jars (jstl.jar & standard.jar) in my webapp's WEB-INF/lib, added the following to my web.xml:
              <taglib>
              <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
              <taglib-location>/WEB-INF/c.tld</taglib-location>
              </taglib>
              and put the follwing two lines at the top of my JSP:
              <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
              <%@ taglib prefix="h" tagdir="/WEB-INF/tags/mytags" %>
              When I browser to my JSP, I get:
              Parsing of JSP File '<...>.jsp' failed:
              <...>.jsp(5): No URI for taglib
              probably occurred due to an error in <...>.jsp line 5:
              <%@ taglib prefix="h" tagdir="/WEB-INF/tags/mytags" %>
              My setup is pretty much straight out of the textbook, so what's wrong? Are tag files, and therefore this form of the taglib directive, not supported by WebLogic?
              Andrew

    Andrew Bickerton wrote:
              > Hi,
              >
              > I'm trying to use Jakarta JSTL 1.0 with BEA WebLogic 8.1 so I can work with tag files. I've put the jars (jstl.jar & standard.jar) in my webapp's WEB-INF/lib, added the following to my web.xml:
              >
              > <taglib>
              > <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
              > <taglib-location>/WEB-INF/c.tld</taglib-location>
              > </taglib>
              >
              > and put the follwing two lines at the top of my JSP:
              >
              > <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
              > <%@ taglib prefix="h" tagdir="/WEB-INF/tags/mytags" %>
              >
              > When I browser to my JSP, I get:
              >
              > Parsing of JSP File '<...>.jsp' failed:
              > ----------------------------------------
              > <...>.jsp(5): No URI for taglib
              > probably occurred due to an error in <...>.jsp line 5:
              > <%@ taglib prefix="h" tagdir="/WEB-INF/tags/mytags" %>
              >
              > My setup is pretty much straight out of the textbook, so what's wrong? Are tag files, and therefore this form of the taglib directive, not supported by WebLogic?
              >
              > Andrew
              81 doesn't support/implement the JSP 2.0 spec (which adds tag files)
              -- Nagesh
              

  • Tagdir Vs uri (in jsp taglib directive).

    Hi
    I am cofused between tagdir and uri used in taglib directive.
    Kindly explain when to use a tagdir and when to use a uri.
    examples :
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
    <%@ taglib tagdir="/WEB-INF/tags" prefix="myTags" %>
    Thanks.

    Hi
    I am cofused between tagdir and uri used in taglib directive.
    Kindly explain when to use a tagdir and when to use a uri.
    examples :
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
    <%@ taglib tagdir="/WEB-INF/tags" prefix="myTags" %>
    Thanks.

  • Taglib directive does not exist error

    hi frieds ,
    i got an error when running jsf application.I used tomcat 5.0.
    My applicatoin tree is
    newjsf
    /java resources
    /mypackage
    /PersonBean.java (java bean)
    /mypackage.messages.properties (properties file)
    /WebConten
    /pages
    /inputname.jsp
    /greeting.jsp
    /WEB-INF
    /faces-config.xml
    /web.xml
    The above is project tree in eclipse.i added necessary jar files in lib and added jsf support.
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <f:loadBundle basename="mypackage.bundle.messages" var="msg"/>
    inputname.jsp file
    ====================
    <html>
    <head>
    <title>enter your name page</title>
    </head>
    <body>
    <f:view> //got error here
    <h1>
    <h:outputText value="#{msg.inputname_header}"/> //got error
    </h1>
    <h:form id="helloForm">
    <h:outputText value="#{msg.prompt}"/> //error
    <h:inputText value="#{personBean.personName}" /> //got error
    <h:commandButton action="greeting" value="#{msg.button_text}" />
    </h:form>
    </f:view>
    </body>
    </html>
    greeting.jsp
    ======================
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <f:loadBundle basename="mypackage.bundle.messages" var="msg"/>
    <html>
    <head>
    <title>greeting page</title>
    </head>
    <body>
    <f:view> //got error
         <h3>
         <h:outputText value="#{msg.greeting_text}" />,
         <h:outputText value="#{personBean.personName}" />
    <h:outputText value="#{msg.sign}" />
         </h3>
    </f:view>
    </body>     
    </html>
    Error is TLD is not found.
    This is my faces-config.xml
    ========================
    <?xml version="1.0"?>
    <!DOCTYPE faces-config PUBLIC
    "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
    "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config>
    <navigation-rule>
    <from-view-id>/pages/inputname.jsp</from-view-id>
    <navigation-case>
    <from-outcome>greeting</from-outcome>
    <to-view-id>/pages/greeting.jsp</to-view-id>
    </navigation-case>
    </navigation-rule>
    <managed-bean>
    <managed-bean-name>personBean</managed-bean-name>
    <managed-bean-class>mypackage.PersonBean</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    </faces-config>
    This is my web.xml
    ====================
    <?xml version="1.0"?>
    <!DOCTYPE web-app PUBLIC
    "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>server</param-value>
    </context-param>
    <context-param>
    <param-name>javax.faces.CONFIG_FILES</param-name>
    <param-value>/WEB-INF/faces-config.xml</param-value>
    </context-param>
    <listener>
    <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
    </listener>
         <!-- Faces Servlet -->
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup> 1 </load-on-startup>
    </servlet>
    <!-- Faces Servlet Mapping -->
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.jsf</url-pattern>
    </servlet-mapping>
    </web-app>
    im using tomcat 5.0. I added all jar files...plz help me...

    Did you "Enable AppXRay" on the project?
    In order to work with Workshop the project needs to be marked as web application.
    If your project is already in workspace, then right click and select "Enable AppXRay" FYI: Workshop identifies web resources inside web-root of an application. A web-root of an application is the folder containing WEB-INF directory.
    Ex:
    - C:\MyProject\WEB-INF\web.xml - in this case MyProject itself will be web-root
    - C:\MyProject\site\WEB-INF\web.xml - in this case site can be web-root
    Once the project is enabled with AppXRay, you open JSP/XML files in Workshop Editor (with Design/Source, Design & Source tabs).
    NOTE: Switch to Workshop perspective (Window > Open Perspective > other > Workshop)to see the default views. The jsp/xml files from AppXplorer view are by default opened in Workshop Editor.
    As I mentioned earlier the following settings should be checked for live "AppXRay" synchronization:
    - Window > Preferences > General > Workspace – make sure “Build automatically” is checked
    - Project > Properties > Builders – make sure “Workshop AppXRay Builder” is present and should be checked

  • Jdev 10.1.3.0.4 jsp 2.0 taglib support

    hi,
    i am trying to use ZK jsp tag library(zkoss.org) for a project. ZK taglib needs jsp2.0 support. i have create a web project with jsp2.0 and servlet2.4.
    then i install taglib to the project and put required libraries under web-inf/lib.
    here is a simple jsp: (just imports taglib)
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <%@ page contentType="text/html;charset=UTF-8"%>
    <%@ taglib uri="http://www.zkoss.org/dsp/web/core" prefix="zkjsp-functions"%>
    <%@ taglib uri="http://www.zkoss.org/jsp/zul" prefix="zuljsp"%>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
    <title>Hello ZK World</title>
    </head>
    <body></body>
    </html>
    when i rebuild the project i get:
    Error(4): Invalid body-content value in TLD: SCRİPTLESS.
    Error(5): Invalid body-content value in TLD: SCRİPTLESS.
    Error(5): "http://www.zkoss.org/jsp/zul" is not a registered TLD namespace
    am i missing something?
    does jdeveloper 10g really supports jsp2.0 taglibs?
    regards, Engin.

    hi,
    jsp tag library definitions exist both at global jsp tag libs and project tag libs.
    my pc regional setting are turkish. i have changed then to english. then the error changed to:
    Error(4): Invalid body-content value in TLD: NONE.
    Error(5): Invalid body-content value in TLD: NONE.
    i guess the taglib file contains none value while its schema definition does not allow this? could it be the reason for last error? i found some none values at tld file.
    regards, engin.

  • "No tag library could be found with this URI" error while compiling jsp

    I am using WebLogic Server 9.2 MP1, JDK 1.5.0_09, Struts 1.3.5
              I am pre-compiling jsp pages with wlappc ant task. However, I got following errors when a jsp page contains ant taglib:
              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.
              The jsp page looks like:
              <%@ taglib uri="http://struts.apache.org/tags-html" prefix="html" %>
              wlappc complains taglib could not be retrieved from this uri. Actually, since Struts 1.3.5, those ".tld" files are contained in strust-taglib-1.3.5.jar, folder META-INF/tld/. And I don't need to set anything in web.xml <tag-lib> tab anymore.
              All the jsp pages can be successfully compiled while being deployed to Server. So what am I missing? My build.xml file looks like:
                   <target name="compile-jsp">
                        <wlappc source="${src.dir}" output="${out.dir}"
                             keepgenerated="true" optimize="true" classpathref="wl_classpath"/>
                   </target>
              where "wl_classpath" contains all the struts related jar files, e.g. struts-core-1.3.5.jar, struts-taglib-1.3.5.jar, ...., and weblogic related jars, e.g. weblogic.jar.....
              I checked "beehive" samples coming with weblogic92, and found it pretty much did the same thing regarding build script and jsp files. So I am totally lost!
              Please help me out. Many thanks.
              Edited by jqian at 02/02/2007 10:24 AM

    Yes sorry, you're correct. The uri I mentioned is just 1.0.
    Do you have the "Oracle WebLogic Web App Extension" Facet for your web project? If not, try adding that and making sure that there is a weblogic.xml file created in the WEB-INF dir. The weblogic.xml file allows you to deploy usig a shared lib for JSTL. It should contain a library-ref element something like the following, with a version of 1.1.
    <wls:library-ref>
    <wls:library-name>jstl</wls:library-name>
    <wls:specification-version>1.1</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>

  • Working with taglibs in jdev 10.1.3.4 (to be used for facelets)

    Short question:
    How do I get the jdeveloper to accept this declaration: <em>&lt;%@taglib uri="http://java.sun.com/jsf/facelets" prefix="ui"%&gt;</em> and its elements, such as <em>&lt;ui:include&gt;</em> ?
    Full story:
    I've been trying to get facelets to work in a project I'm working on. A part of this project, which I have no control over, is automatic javascript insertion via xslt, which makes it impossible for me to use xml style documents. (due to '&lt;'&gt;' being used for comparison, rather than tag opening/closing. Having said that, here's my problem:
    I want to use jsf / facelets to create a template page, that will be used in about 30 other pages. If I was able to use an xml-style jsp docuement, I could add an xmlns:ui, and faces support would work. However, since the above is true, I have to define the taglib in jsp style, to be able to use facelets. This would look something like:
    <blockquote>
    <em>&lt;%@taglib uri="http://java.sun.com/jsf/facelets" prefix="ui"%&gt;</em>
    </blockquote>
    Upon doing this, jdeveloper tells me that
    <blockquote>
    <em>Error(7): "http://java.sun.com/jsf/facelets" is not a registered TLD namespace</em>
    </blockquote>
    and for any uses thereof:
    <blockquote>
    <em>Error(33): ui:include is not a registered tag in that namespace.</em>
    </blockquote>
    After I add the jsf-facelets.jar library (tried versions 1.0.1.14, 1.1.11, 1.1.14), nothing changes.
    I understand that Jdeveloper wants to validate the taglibs I define, but there is no tld in the jsf distribution and there also should be no need for this (in xml-style syntax, it works fine without validation).
    If there's any way I can skip this validation or make jdeveloper believe the library is valid, I'm done. However, I have not been able to find such a function.
    Some guy from exadel has uploaded a tld for facelets to the facelets project (it's under contrib, here ). This tld has been referenced in most threads that deal with the problem (jsf in jdeveloper). The tld can't however provide a structural solution, since it's not complete. The &lt;tag-class&gt; and &lt;tei-class&gt; tags within the tld are empty. Reason enough for jdeveloper to halt on it.
    Adding the library to jdeveloper would be done thus: go to tools, go to 'manage libraries', go to 'tag libraries' click 'user' and select 'new'. Browse your way trough your filesystem and locate the tld file. Add a reference to the jsf-facelets and a reference to the el-api and el-impl jars and click ok. Then go to project properties and under tag lib libraries, add this library.
    Jdeveloper responds to this with the following error:
    <blockquote>
    <em>Error(33): Unable to instantiate tag: ui:include (class: null) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.</em>
    </blockquote>
    Right. To be able to instantiate the tag, jdeveloper seems to not only need the description of the tag, but also the connection to the real thing. I've been exploring the jsf-facelets jar and came to the conclusion that the tags in the tld correspond to the classes in the 'com.sun.facelets.tag.ui.' package, so for ui:include, that would be 'com.sun.facelets.tag.ui.IncludeHandler'.This class, described here here, seems indeed to have the same attributes as our ui:include tag. Tag tei-tag (tag extra information), is, afaik, not mandatory, so I'll leave it empty. Rebuild in developer gave me lots of errors when I did it the first time (which I solved by filling in the other tag-classes), but when recreating it for this topic, I had no problems of that sort. The error I'm stuck with is:
    <blockquote>
    <em>Error(33): src is not a property of com.sun.facelets.tag.ui.IncludeHandler</em>
    </blockquote>
    I'm baffled by this statement. The tld says this property exists, the ui:include documentation agrees with me and the file I'm linking to has a src TagAttribute (for which I'm having trouble finding the setter, but it worked in the xml-style version). Using this tld Jdeveloper grants content assistance, which suggests to me that I should use the src tag. It is mandatory.
    I tried to fill in the &lt;tei-class&gt;'es, but the facelets jar contains no class (that extends from) tagExtraInfo, as far as I could see. Using the one from jsf (facelets are, in a manner, jsf tags, being just a viewHandler for jsf), didn't change anything.
    At this point, I'm stumped. I hope there is either
    - a way to disable the tld resolution feature
    - a way to make a change in the tld I have now and make jdeveloper parse this tld
    - a way to create some dummy tld that jdeveloper will accept
    <blockquote>
    <em>Error(33): src is not a property of com.sun.facelets.tag.ui.IncludeHandler</em>
    </blockquote>
    How can I get rid of this error? Thanks for any suggestions!
    edit: fixed some typos and messed-up links on 04-Nov-2008 04:35
    Edited by: user2103934 on 04-Nov-2008 06:07

    Opon further expirimentation, I've discovered that the facelets view handler can not handle the <%@ taglib > declaration, returning me an
    com.sun.facelets.FaceletException: Error Parsing /mapviewer.jsp: Error Traced[line: 3] <Line 3, Column 2>: XML-20201: (Fatal Error) Expected name intead of %.
    With the facelets handler off, the non-xml facelet declaration is handled fine, but is no help.
    Which means I'm bound to use the xml style for facelets, which means I'm going to have to catch the inserted javascript in some manner.
    In any case, the original question in this topic is not the problem anymore, so I closed it here and awarded 5 points for a helpful answer.
    Edited by: rjonkman on 05-Nov-2008 07:17

  • Jsp taglibs in include files not detected, throws errors, no code insight

    I have a jsp which is included in all the other jsp. it looks something like this
    taglibs.jsp
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>
    <%@ taglib uri="http://www.springframework.org/tags" prefix="spring" %>
    <%@ taglib prefix="form" uri="http://www.springframework.org/tags/form" %>
    test.jsp
    <%@ include file="/jsp/menu/taglibs.jsp"%>
    <html>
         <head>
              <title>Tours</title>
         </head>
         <body>
    <form:form commandName="testCommand">
                   <form:hidden path="tour.firstname" id="tour.firstname" />
    and so on.
    I am having 2 problems
    1. the jsp editor show errors all over the place saying
    element path not expected
    element commandName not expected etc.
    2. no code insights.
    but if i include the taglib def in test.jsp it dosn't show any error and also provides code insights. but seldom do people include all taglibs in all jsps.
    is there a way for Jdeveloper to show code insights in jsp pages which includes a jsp or like xml schemas could be added at some place(tools-pref-xml schemas) and when used anywhere, would provide code insights.

    am not sure, try with this
    <jsp:include   .../>

Maybe you are looking for

  • Article Deletion in SAP Retail

    What is the process for deleting an article and then archiving the article in SAP Retail ECC6.0?  So far what I have is to: 1.  Go to MM46 and find layouts for article 2.  Go to WLWBN and Delete Assignments 3.  Go to Assortment in WSP6 and delist fro

  • Word 2007 to PDF = no bookmarks

    Hi, We recently got upgraded to Office 2007. And we use Adobe Acrobat 6.0 Standard. The OS is Windows XP. Now, when we try to convert Word documents to PDF, the PDF converts without any bookmarks. I checked the settings in Acrobat and I have option t

  • Image and .WAR

              Hi,           I'm using weblogic 6.1 with sp2.           I have deployed the web application with an .ear file.           All my JSPs and servlets are working strong.           But 10% of the images that are being shown by the browser are v

  • Write to i2c Register from java

    My setup: Java 1.5, SUSE Linux 10.2 I'm trying to set registers over i2c. From command line this can be done using "i2cset [options] [bus_address] [chip_address] [register] [value] b". I'd like to do this without using the command line, directly from

  • Trying to download pics form iphone4 and got this message The operation couldn't be completed. (com.apple.ImageCaptureCore error -9912.)

    why cant i donwload my pics and videos with my iphone 4 using preview? It says The operation couldn't be completed. (com.apple.ImageCaptureCore error -9912.)