wood burning stoves 2.0*
The moose likes Clojure and the fly likes  No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Languages » Clojure
Bookmark " No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or" Watch " No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or" New topic
Author

No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or

srinu dodda
Greenhorn

Joined: Nov 29, 2010
Posts: 3
Hi,
i have got following err while running app in weblogic 10.3
please any one could help me..

login.jsp:3:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %>
^----^
login.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 uri="/WEB-INF/struts-html-el.tld" prefix="html" %>
^----^
login.jsp:3:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %>
^----^
login.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 uri="/WEB-INF/struts-html-el.tld" prefix="html" %>
^----^
login.jsp:4:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-bean-el.tld" prefix="bean" %>
^----^
login.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 uri="/WEB-INF/struts-bean-el.tld" prefix="bean" %>
^----^
login.jsp:4:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-bean-el.tld" prefix="bean" %>
^----^
login.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 uri="/WEB-INF/struts-bean-el.tld" prefix="bean" %>
^----^
login.jsp:5:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-logic-el.tld" prefix="logic" %>
^----^
login.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="/WEB-INF/struts-logic-el.tld" prefix="logic" %>
^----^
login.jsp:5:5: Invalid tag library.
<%@ taglib uri="/WEB-INF/struts-logic-el.tld" prefix="logic" %>
^----^
login.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="/WEB-INF/struts-logic-el.tld" prefix="logic" %>
^----^
login.jsp:6: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://java.sun.com/jstl/core" prefix="c" %>
^----^
login.jsp:6: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://java.sun.com/jstl/core" prefix="c" %>
^----^
login.jsp:7: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://java.sun.com/jstl/fmt" prefix="fmt" %>
^----^
login.jsp:7: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://java.sun.com/jstl/fmt" prefix="fmt" %>
^----^
Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

Not the suitable forum to ask, please wait till moderators move it to the appropriate one.
 
GeeCON Prague 2014
 
subject: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or