Tag Library Compile Warning

Why does the weblogic jsp compiler wine about this standard tag library
          descriptor DTD?
          <?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">
          Have yet to see a TLD that does not use precisely this string and yet
          weblogic whines constantly about it.

I figured it out. Under the Configuration/TagLibraries,
create a CrossTagAttr folder and stick a .vtm file in it. In the
.vtm file, use the <crosstag_attributes> tag and its
children. See Configuration/TagLibraries/CrossTagAttr/Spry/Spry.vtm
for an example.

Similar Messages

"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>

USING STRUTS2 DOJO PLUGIN TAGS GIVES COMPILER ERROR (JDev 10.1.3.3)

Hi.
Using Struts 2.1.2 dojo plugin tags gives compiler error:
Error(9): Couldn't instantiate tag sx:head (class: null). Be sure that the tag class is available...
(translated from spanish)
So I can't run the application.
When configured, tags can be chosen from the component palette and the normal struts tags (not the dojo ones) do compile and run ok.
From service request:
Examining Jdeveloper's console message, its apparent that the tag library is not compatible with JDeveloper because of
the following warning:
oracle.jsp.logger.JspMessages.warningInvalidTldVersion:J2EE JSP-0033
Someone has any workaroun or solution?
### Steps to Reproduce ###
1.- Create new application and project
2.- Copy Struts 2.1.2 jar libs including dojo somewhere (for example in WEB-INF/lib)
3.- Associate the jars to the project (Libraries option in Project Properties)
4.- Create a JSP
5.- Use a dojo tag in the JSP
<%@ taglib uri="/struts-dojo-tags" prefix="sx"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
<title>index</title>
<sx:head/>
</head>
<body></body>
</html>
6.- Compile

Hi did you solved this problem? I have same

Error in using struts tag library

Platform information:
Windows XP
BEA Weblogic Server 8.1 (Developer)
Struts 1.1
I am unable to compile the following JSP in weblogic because it says there is
an error using the struts-html tag library. (Details about the error are mentioned
after the JSP)
My JSP file is:
===================================================================
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri='/WEB-INF/struts-template.tld' prefix='template' %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<%@ page import="com.hipaaccelerator.runtime.HARuntime" %>
<jsp:useBean id='logonForm' scope='request' class='com.hipaaccelerator.hipaax.form.LogonForm'/>
<html:html>
<head>
<title>Logon</title>
<link rel='stylesheet' href="<html:rewrite page='/styles/default.css'/>" type='text/css'
>
<script language='javascript' src="<html:rewrite page='/scripts/default.js'/>"
type='text/javascript'></script>
</head>
<body>
<html:form action='/logon.do' >
     <table border='0' align='center' >
          <tr><td height='10'></td></tr>
          <tr>
<td align='center'>
<html:img src='/images/Logo.gif' height='70'
width='449'/>
</td>
</tr>
          <tr><td height='10'></td></tr>
     </table>
     <table align='center' width='100%' >
     <tr><td height='10'></td></tr>
     <tr>
     <td height='20' width='10%'> </td>
     <td height='20' colspan='3' align='center' style="font-size: 18pt; color:
blue;
background-color: white; text-align:center">PAC
</td>
     <td height='20' width='10%'> </td>
     </tr>
     <tr><td height='10'></td></tr>
     <tr>
     <td height='20' width='10%'> </td>
     <td height='20' width='8%'> </td>
     <td height='20' align='center' style="border-style:solid; border-width:2pt;
font-
size: 10pt; color: red; background-color: white; text-align:center">
<%= HARuntime.instance().getConfig().getProperty("logonAnnouncement")
%>
</td>
     <td height='20' width='8%'> </td>
     <td height='20' width='10%'> </td>
     </tr>
     <tr><td height='10'></td></tr>
     </table>
     <table border='0' align='center' >
     <tr>
<td class='formfieldname' ><b>User Name: </td>
     <td class='formfield'>
     <html:text property='username' maxlength='20' size='20'/>
     </td>
     </tr>
     <tr><td class='formfieldspacer'></td></tr>
     <td class='formfieldname' ><b>Password:</b> </td>
     <td class='formfield'>
     <html:password property="password" size="20" maxlength="20"
redisplay="false"/>
     </td>
     </tr>
     <tr><td class='formfieldspacer'></td></tr>
     <tr>
<td colspan='2' align='middle'>
     <html:image src='/images/login.gif' onclick='document.forms[0].submit();
return false;' />
     </td>
</tr>
</table>
<br><br>
</html:form>
</body>
</html:html>
===================================================================
The translation of this page fails with the following error:
<Dec 16, 2003 5:06:13 PM MST> <Error> <HTTP> <BEA-101045> <[ServletContext(id=4595,name=hipaax,context-path=/hipaax)]
translation of /logon.jsp failed:
weblogic.servlet.jsp.JspException: (line 1): Error in using tag library uri='/WEB-INF/struts-html.tld'
prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag' has no setter
method corresponding to TLD declared attribute 'server', (JSP 1.1 spec, 5.4.1)>
===================================================================
I have struts.jar in /web-inf/lib. I have taglib (uri and location) definitions
in web.xml.I have all the struts tld files under /web-inf. Is there anything
else I have to do?
Any help would be greatly appreciated.
Thank you.
Sharmila

Update: I just looked up the WL version and it's 8.1 sp3
          So, I guess, JSTL 1.1 (which includes jstl fn tags) is not supported by WL.... Someone correct me if I am wrong.
          Thanks,
          pal :)

The tag handler gridcolumn does not have a setter for the attribute autoExpand specified in the Tag Library Descriptor.

I recently moved from coldfusion 8 to coldfusion 9 but all the pages with cfgrid: is throwing the following error. Any suggestion would be of great help
coldfusion.jsp.JRunTagLibraryInfo$NoSuchAttributeException: The tag handler gridcolumn does not have a setter for the attribute autoExpand specified in the Tag Library Descriptor.
at coldfusion.jsp.JRunTagLibraryInfo.getPropertyType(JRunTagLibraryInfo.java:627)
at coldfusion.jsp.JRunTagLibraryInfo.buildTagInfo(JRunTagLibraryInfo.java:585)
at coldfusion.jsp.JRunTagLibraryInfo.getTag(JRunTagLibraryInfo.java:267)
at coldfusion.compiler.NeoTranslationContext.findTagName(NeoTranslationContext.java:346)
at coldfusion.compiler.NeoTranslationContext.isKnownTag(NeoTranslationContext.java:222)
at coldfusion.compiler.CFMLParserBase.isKnownTagName(CFMLParserBase.java:589)
at coldfusion.compiler.cfml40TokenManager.TokenLexicalActions(cfml40TokenManager.java:6704)
at coldfusion.compiler.cfml40TokenManager.getNextToken(cfml40TokenManager.java:6586)
at coldfusion.compiler.cfml40.getToken(cfml40.java:11879)
at coldfusion.compiler.CFMLParserBase.isTrivialAngleBracket(CFMLParserBase.java:707)
at coldfusion.compiler.cfml40.jj_3_1(cfml40.java:9392)
at coldfusion.compiler.cfml40.jj_3_2(cfml40.java:9460)
at coldfusion.compiler.cfml40.jj_3R_67(cfml40.java:9500)
at coldfusion.compiler.cfml40.jj_3_86(cfml40.java:8147)
at coldfusion.compiler.cfml40.jj_3R_92(cfml40.java:8584)
at coldfusion.compiler.cfml40.jj_3_85(cfml40.java:8641)
at coldfusion.compiler.cfml40.jj_2_85(cfml40.java:7619)
at coldfusion.compiler.cfml40.cfml(cfml40.java:4215)
at coldfusion.compiler.cfml40.cfif(cfml40.java:311)
at coldfusion.compiler.cfml40.cfml(cfml40.java:4224)
at coldfusion.compiler.cfml40.cfif(cfml40.java:311)
at coldfusion.compiler.cfml40.cfml(cfml40.java:4224)
at coldfusion.compiler.cfml40.cfelse(cfml40.java:442)
at coldfusion.compiler.cfml40.cfelseif(cfml40.java:374)
at coldfusion.compiler.cfml40.cfif(cfml40.java:314)
at coldfusion.compiler.cfml40.cfml(cfml40.java:4224)
at coldfusion.compiler.cfml40.start(cfml40.java:4664)
at coldfusion.compiler.NeoTranslator.parsePage(NeoTranslator.java:667)
at coldfusion.compiler.NeoTranslator.parsePage(NeoTranslator.java:648)
at coldfusion.compiler.NeoTranslator.parseAndTransform(NeoTranslator.java:401)
at coldfusion.compiler.NeoTranslator.translateJava(NeoTranslator.java:343)
at coldfusion.compiler.NeoTranslator.translateJava(NeoTranslator.java:144)
at coldfusion.runtime.TemplateClassLoader$TemplateCache$1.fetch(TemplateClassLoader.java:418 )
at coldfusion.util.LruCache.get(LruCache.java:180)
at coldfusion.runtime.TemplateClassLoader$TemplateCache.fetchSerial(TemplateClassLoader.java :362)
at coldfusion.util.AbstractCache.fetch(AbstractCache.java:58)
at coldfusion.util.SoftCache.get_statsOff(SoftCache.java:133)
at coldfusion.util.SoftCache.get(SoftCache.java:81)
at coldfusion.runtime.TemplateClassLoader.findClass(TemplateClassLoader.java:591)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:80)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:53)
at coldfusion.CfmServlet.service(CfmServlet.java:201)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 )
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Thanks Vishu,
We are running Coldfusion 9 and attach is the sample code and error message.:
The tag handler gridcolumn does not have a setter for the attribute autoExpand specified in the Tag Library Descriptor.
The CFML compiler was processing:
A cfgrid tag beginning on line 39, column 18.
The error occurred in E:/Websites/DreData/sobrietytesting/main/Sobrietytesting/Admin/view_users.cfm: line 54
52 :                     hrefkey="member_id"
53 :                     bind="cfc:tabledisplay.browseAccessAcountRequests(,,,)"
54 :                     >
55 :

Commerce server 3.2 tag library error

I have installed the following components on Solaris 2.7:-
- Java1.3
- WebLogic5.1
- SP6
- Commerce Server 3.2
The commerce server seems to start fine except the following exception
when the Create User button is clicked from the Admin screen. Any help
is appreciated.
Leo
6th Dimension-
Tue Jan 02 11:14:15 PST 2001:<I> <WebAppServletContext-tools> *.jsp:
init
Tue Jan 02 11:14:15 PST 2001:<I> <WebAppServletContext-tools>
FlowManager: init
Tue Jan 02 11:14:26 PST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:141)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Tue Jan 02 11:14:26 PST 2001:<I> <ServletContext-General> servletimages:
init

To be more specific, I put the jar file in the $WEBLOGIC_HOME/lib directory.
-Brad.
"Brad Christiansen" <[email protected]> wrote:
>
I was getting the same exception until I put the weblogic-510-tags.jar file (found in the SP6 zip file) in a directory referenced by the WEBLOGIC_CLASSPATH environment variable.
-Brad.
Leo Fu <[email protected]> wrote:
I have installed the following components on Solaris 2.7:-
- Java1.3
- WebLogic5.1
- SP6
- Commerce Server 3.2
The commerce server seems to start fine except the following exception
when the Create User button is clicked from the Admin screen. Any help
is appreciated.
Leo
6th Dimension-
Tue Jan 02 11:14:15 PST 2001:<I> <WebAppServletContext-tools> *.jsp:
init
Tue Jan 02 11:14:15 PST 2001:<I> <WebAppServletContext-tools>
FlowManager: init
Tue Jan 02 11:14:26 PST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:141)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Tue Jan 02 11:14:26 PST 2001:<I> <ServletContext-General> servletimages:
init

No tag library could be found with this URI

Hi,
          I am trying to deploy the duke application on weblogic 9.2. I have deployed the application is exploded format using the admin console and its in active state.
          When I try to access http://localhost:7001/hello1, I get the following error:
          Compilation of JSP File '/index.jsp' failed:
          index.jsp:28: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/jsp/jstl/core" prefix="c" %>
          ^----^
          index.jsp:29: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/jsp/jstl/functions" prefix="fn" %>
          ^----^
          Below are the files used
          web.xml(under WEB-INF)
          ======================
          <?xml version="1.0" encoding="UTF-8"?>
          <web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee">
          <display-name>WorkBench War</display-name>
          <description>WorkBench War that contains all the JSP files</description>
          <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
          </welcome-file-list>
          </web-app>
          weblogic.xml
          ============
          <?xml version="1.0" encoding="UTF-8"?>
          <wls:weblogic-web-app xmlns:wls="http://www.bea.com/ns/weblogic/90">
          <wls:context-root>/hello1</wls:context-root>
          </wls:weblogic-web-app>
          index.jsp
          =========
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/functions" prefix="fn" %>
          <html>
          <head><title>Hello</title></head>
          <body bgcolor="white">
          Hello, my name is Duke. What's yours?
          <form method="get">
          <input type="text" name="username" size="25">
          <input type="submit" value="Submit">
          <input type="reset" value="Reset">
          </form>
          <c:if test="${fn:length(param.username) > 0}" >
          <%@include file="response.jsp" %>
          </c:if>
          </body>
          </html>
          with regards
          Mahesh Acharya

This got resolved after I copied the jstl.jar and standard.jar from ajakarta site under WEB-INF/lib.
          Now I get the following error :-(
          index.jsp:1:1: Unable to load the validator class: "org.apache.taglibs.standard.tlv.JstlCoreTLV".
          <%--
          ^---
          --%>
          ---^
          index.jsp:44:2: The tag handler class was not found "org.apache.taglibs.standard.tag.rt.core.IfTag".
          <c:if test="${fn:length(param.username) > 0}" >
          ^--^
          index.jsp:44:2: The tag handler class was not found "org.apache.taglibs.standard.tag.rt.core.IfTag".
          <c:if test="${fn:length(param.username) > 0}" >
          ^--^

Tag library 'div' hook

Well, 'div' is not corrupt, but the application programming related to customization of Tag libraries is corrupt.
What is happening:
When Dreamweaver CC is installed, and when it opens fresh html files, it makes a mess of line breaks and indents in the text layout of the code. Using the menu item Commands / Apply source formatting also makes a mess, This menu command mess is a slight improvement over the horrendous mess that Dreamweaver CC makes of code when it opens and when it periodically 'refreshes' the files that it trashes. However, the code is not usable, as with more advanced css and html technique, the code becomes unreadable for Chrome, Internet Explorer, Safari, and presumably all browsers.
DW's mess described:
All indents are as spaces, making manual clean-up repetitive, necessary and extremely tedious.
The head and body tags are indented far inside their content, and that content is also erratically indented.
The use of Tag library editor would seem the expected user path, in seeking a user resolution, and perhaps in defining a programmatic intervention.
All tags are trashed, put going to the heart of the html cascade, we start with the p tag: e.g., p tag in Tag libraries defaults as
Line breaks: before and after tag
Contents: formatted and indented
Case: default
We try numerous combinations of p tag settings in the noted dialog interface.
The p tag settings do not appear to effect the mess. Dreamweaver, ignores default and manual settings, sometimes shuffling the mess a little, but minor shuffling only occurring twice, and without any tag block line break changes.
Perhaps, for a given instance of Dreamweaver installation, within a given simple document's system interface, Dreamweaver settings may reveal something called a 'performance hook' by application programmers. Perhaps we can isolate a hook that is useful for the Adobe support; support that lacking professional attention has maintained Dreamweaver as a failed application for over a year (since October 2012) on my Windows desktop. We move next to the div tag.
Manual intervention 'exposes bad behavior of div tag' hook:
Our simple document layout is... simple. Deploying doctypes for both html5 and xhtml transitional and deploying internal and external style methods, with the same code trashing result, we correctly layout tags as HEAD, BODY, DIV and P. Beginning with the p tag, various tag library settings are applied to determine effect on Apply source formatting command. Various p tag settings have no effect, and p is returned to its DW default setting, as noted above. The following div tag settings disable Apply source formatting command's code trashing specifically of line indents.
Line breaks: before and after tag
Contents: formatted but not indented
Case: default
Unfortunately, with this setting, line breaks between only some tags are maintained during Dreamweaver's auto code trashing (e.g., between closing head and opening body tag): sometimes when Dreamweaver does it's auto (or manual) trashing, these specific line breaks, between block tags, are not preserved. However, with this Tag library setting for the div tag using the noted basic cascade, all tag indents are ignored. But only when code is manually kept against left margin, without any indentation. And, ONLY WITH DIV TAG HOLDING THESE PARTICULAR SETTINGS, FOR THIS PARTICULAR DOCUMENT!
FLAT CODE is preferable to the bigger mess that Dreamweaver routinely imposes as it auto trashes code. Also, allowing any left margin indentation worsens Dreamweaver's code trashing... so, given Dreamweaver's chaotic destructiveness, I don't know if it is correct to imply any significance to my manual Tag library settings management, but it is clear that Dreamweaver is unable to correct the mess it makes, using the manual Apply source formatting command. And this is the first 'performance hook' that has been defined for my desktop in over 400 days. But setting div tag in this way is the only way to stop Dreamweaver trashing code layout line indents (trashing that occurs both during Dreamweaver automatic actions and with user menu action, for the specific noted html layout - a layout that is far too basic to be useful for 99.9% of design work). But only for a given instance of Dreamweaver installation for a given OS installation, and not across OS installations, or with any other file than the file (or files, in relational assessment) targeted for our 'hook' presentation analysis.
Conclusion:
Dreamweaver trashes code layout every time the application applies code formatting (e.g., opening new documents from other sources, applying menu commands, etc.). That is, all user code layout will be trashed by Dreamweaver. However, a specific div tag setting in Tag library editor may maintain a single instance for manual correction of Dreamweaver code trashing, when basic page layout is used with div in the noted cascade, and with div settings manually corrected as noted. This is a hopelessly unacceptable condition that the Dreamweaver application imposes on design work for my Windows 8.1 operating system. Professional designers of global significance and stature using many variants of Mac and PC systems have warned me not to use Dreamweaver, recommending numerous alternatives. I am taking the position that Adobe retains a shred of marketplace survivability, and therefore will promptly fix minor problems when I bring them to Adobe's attention.
IMPORTANT:
Obviously, this is not acceptable application performance. Is support available to Adobe that will now, immediately repair the Dreamweaver application that I use as a paid subscription to eliminate systematic code trashing?

I figured it out. Under the Configuration/TagLibraries,
create a CrossTagAttr folder and stick a .vtm file in it. In the
.vtm file, use the <crosstag_attributes> tag and its
children. See Configuration/TagLibraries/CrossTagAttr/Spry/Spry.vtm
for an example.

Weblogic 12c : Spring taglib No tag library could be found with this URI

Hello,
I have an application which deploy perfectly on JBOSS 7 and Websphere
My WAR includes WEB-INF/lib/spring-webmvc.jar which contains all .tld files declaration (stardard stuff up to now....)
When I try to acces ths page (JSP) I got : No tag library could be found with this URI
Really don't know why ??

I think that there is bug in JSP precompilation by weblogic 12c maven plugin and appc. Seems me that jsp compiler can lose sometimes tag libraries it's precompiling. Next retry using exactly same pom can be successful. I get same results using command line and OEPE 12.1.1.0 mave(pom). My java options for maven package are(-Xmx1024m -Xms1024m -XX:PermSize=512m).
When I get the error it's something like
"Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:appc (default) on project ui_elements:
There are 1 nested errors:
weblogic.utils.compiler.ToolFailureException: jspc failed with errors :weblogic.servlet.jsp.CompilationException: naviButtons.tag:23:6: The tag handler class was not found "jsp_servlet._tags.__pagelink_tag".
<T:pageLink url="${naviStatus.previousPage.linkUrl}"
^--------^
naviButtons.tag:23:6: The tag handler class was not found "jsp_servlet._tags.__pagelink_tag".
<T:pageLink url="${naviStatus.previousPage.linkUrl}"
Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:appc (default) on project ui_elements:"
Next unsuccessful compilation can mention different tags. Very irregular behavior.
Do you have resolution?

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

Intermedia tag library in Jdeveloper

Has any one had trouble getting the Intermedia tag library to compile in Jdeveloper? I keep getting an exception Java class OrdmediaUsing missing or invalid???

Go to "project settings" In "profiles" you will see a "Libraries" item, click on that for Deevelopment and other profiles. There will be an "Oracle interMedia" item there. Include it as a "Selected Library".
Larry

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

Tag Library Error

I am using Jdeveloper and BEA Weblogic 8.1 application server environment.
I have custom tag and tld file for the tag. When I try to compile it , I am getting this error which just points to the begininng of the jsp file which uses the tag.
Error: java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo.<init>(Ljava/lang/String;ZLjava/lang/String;ZZ)V
I've tried searching online and found that it may be caused by the the wrong jar reference in classpath. I've tried adding whole bunch of different versions of servlet.jar to my classpath in the project properties but I am still getting the same error.
Please advice
Mikhail

I've tried putting weblogic.jar into the web-inf/lib folder and also added library reference in the project properties but that did not fixed it.
I still receive this error in all jsp files where I have a tag:
Error: java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo.<init>(Ljava/lang/String;ZLjava/lang/String;ZZ)V
Here's the content of my simple tld file:
<?xml version="1.0" encoding="UTF-8" ?>
<!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.0</tlib-version>
<jsp-version>1.1</jsp-version>
<short-name>Bima Tags</short-name>
<description>Application tag library for the BIMA Application</description>
<tag>
<name>navbar</name>
<tag-class>com.arrownacp.bima.tags.NavBarTag</tag-class>
<body-content>empty</body-content>
<description>Display the Navigation Bar</description>
<attribute>
<name>pageName</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
<type>java.lang.String</type>
</attribute>
</tag>
</taglib>
This is how I refer to it in my jsp file:
<%@ taglib uri="WEB-INF/BimaTags.tld" prefix="es" %>
and in the page body:
<es:navbar pageName="addUser" />
Need an urgent help, thanks
Mikhail

Error using custom tag library

Hi All,
          I am getting the following error:
          On the browzer page when I invoke the foo.jsp page containing a tag
          library.
          Parsing of JSP File '/jsp/foo.jsp' failed:
          /jsp/foo.jsp(7): Could not parse deployment descriptor:
          org.xml.sax.SAXParseException: Could not parse taglib, starting at
          line 5
          probably occurred due to an error in /jsp/foo.jsp line 7:
          <%@ taglib uri="example-taglib.tld" prefix="eg" %>
          Wed Mar 27 13:17:49 PST 2002
          The configutation is as follows
          Foo.jsp in documentRoot/jsp
          tld file in documentRoot/WEB-INF
          class files in documentRoot/WEB-INF/classes/examples.
          The server is spitting out the following code:
          weblogic.servlet.jsp.JspException: (line 7): Could not parse
          deployment descript
          or: org.xml.sax.SAXParseException: Could not parse taglib, starting at
          line 5
          at java.lang.Throwable.fillInStackTrace(Native Method)
          at java.lang.Throwable.fillInStackTrace(Compiled Code)
          at java.lang.Throwable.<init>(Compiled Code)
          at java.lang.Exception.<init>(Compiled Code)
          at java.lang.RuntimeException.<init>(RuntimeException.java:47)
          at weblogic.servlet.jsp.JspException.<init>(JspException.java:9)
          Can anyone help me with this ?
          Thanks for your help!!
          SundayFunday!


Could anyone please let me know what is going on here?
          SundayFunday!
          [email protected] (SundayFunday) wrote in message news:<[email protected]>...
          > Can anyone help me with this?!!
          >
          > Thanks!
          >
          > Sundayfunday.
          >
          > [email protected] (SundayFunday) wrote in message news:<[email protected]>...
          > > Hi All,
          > >
          > > I am getting the following error:
          > >
          > > On the browzer page when I invoke the foo.jsp page containing a tag
          > > library.
          > >
          > > Parsing of JSP File '/jsp/foo.jsp' failed:
          > > --------------------------------------------------------------------------------
          > > /jsp/foo.jsp(7): Could not parse deployment descriptor:
          > > org.xml.sax.SAXParseException: Could not parse taglib, starting at
          > > line 5
          > > probably occurred due to an error in /jsp/foo.jsp line 7:
          > > <%@ taglib uri="example-taglib.tld" prefix="eg" %>
          > > --------------------------------------------------------------------------------
          > > Wed Mar 27 13:17:49 PST 2002
          > >
          > >
          > >
          > > The configutation is as follows
          > >
          > > Foo.jsp in documentRoot/jsp
          > >
          > > tld file in documentRoot/WEB-INF
          > > class files in documentRoot/WEB-INF/classes/examples.
          > >
          > >
          > >
          > > The server is spitting out the following code:
          > >
          > > weblogic.servlet.jsp.JspException: (line 7): Could not parse
          > > deployment descript
          > > or: org.xml.sax.SAXParseException: Could not parse taglib, starting at
          > > line 5
          > > at java.lang.Throwable.fillInStackTrace(Native Method)
          > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
          > > at java.lang.Throwable.<init>(Compiled Code)
          > > at java.lang.Exception.<init>(Compiled Code)
          > > at java.lang.RuntimeException.<init>(RuntimeException.java:47)
          > > at weblogic.servlet.jsp.JspException.<init>(JspException.java:9)
          > >
          > >
          > > Can anyone help me with this ?
          > >
          > > Thanks for your help!!
          > >
          > > SundayFunday!

Error while using Tag Library in Weblogic !

Hi,
I am trying to run a JSP in weblogic which makes use of tag library in it. I am getting the following error
C:\bea\weblogic81\samples\domains\examples\.\examplesServer\.wlnotdelete\extract\examplesServer_Bidla_Bidla\jsp_servlet\_registration\__finish.java:192: cannot resolve symbol
probably occurred due to an error in /Registration/Finish.jsp line 29:
<as:email>
Corresponding Full compiler error(s): is
C:\bea\weblogic81\samples\domains\examples\.\examplesServer\.wlnotdelete\extract\examplesServer_Bidla_Bidla\jsp_servlet\_registration\__finish.java:192: cannot resolve symbol
symbol : variable EVAL_BODY_BUFFERED
location: interface javax.servlet.jsp.tagext.BodyTag
if (_int0 == BodyTag.EVAL_BODY_BUFFERED) { //[ /Registration/Finish.jsp; Line: 29]
^
I have 10 errors like this, just for simplicity, I haven't posted them all.
The JSP runs fine with Tomcat.
I don't have servlet.jar anywhere in my classpath nor in my application\WEB-INF\lib
Please help.
Thanks !

Hi,
I am still facing the same problem even after placing servlet.jar and struts.jar files in application\WEB-INF\lib\ directory. Can you please guide me what may be the reason for it.
Thanks in advance.
Regards,
Prashanth.

Tag Library Compile Warning

Similar Messages

Maybe you are looking for