blocks|key|2458962|text|这在很大程度上取决于它是什么样的项目。WTP的JSP支持要么希望JSP文件位于Web文件夹的父文件夹下(src/web，然后将其视为"/“以查找TLDs)，要么将项目元数据设置为帮助它知道根目录位于何处(通过部署程序集在动态Web项目中为您完成)。您是如何引用TLD文件的，JSP文件位于何处？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2458963|也许我错过了Eclipse论坛的原始帖子；我看到的那篇文章是在这个论坛之后整整一天发布的。|2458964|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A lot depends on what kind of project it is. WTP's JSP support either expects the JSP files to be under the same folder that's the parent of the WEB-INF folder (src/web, which it will then treat as "/" to find TLDs), or to have project metadata set up to help it know where that root is (done for you in a Dynamic Web Project through Deployment Assembly). How are you referring to the TLD file, and where is the JSP file located?

And maybe I missed the original post to the Eclipse forums; the one I saw was posted a full day after this one.

blocks|key|933121|text|我今天解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933122|将输出目录更改为WEB/classes文件夹。(项目/属性/Java构建路径，默认输出文件夹)|unordered-list-item|933123|分配模块依赖项。(Project/Properties/Java模块依赖项)它们将被复制到WEB/+lib文件夹中，Eclipse也在其中查找标记库定义。|933124|希望能帮上忙。|933125|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

I fixed this problem today. 

<ul>
<li>Change your output directory to your WEB-INF/classes folder. (Project/Properties/Java Build Path, Default output folder)</li>
<li>Assigne the module dependencies. (Project/Properties/Java EE Module Dependencies) they will be copied to the WEB-INF/lib folder where Eclipse looks for the tag lib definitions too.</li>
</ul>

I hope it helps.

blocks|key|997353|text|MyEclipse和Eclipse6.6.0也有同样的问题。它将uri值排列在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|997354|<%25@+taglib+prefix="s"+uri="/struts-tags"%25>。我通过“Project/MyEclipse/Web/Tag库”修复了它，并将Struts1.2的默认TLD前缀设置为's‘。我还必须在‘Project/MyEclipse/Web/配置工作区设置./标记库’下进行同样的操作。|offset|length|style|CODE|997355|entityMap^0|0|0|16|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had the same problem with MyEclipse and Eclipse 6.6.0. It red lined the uri value in every 

<code>&lt;%@ taglib prefix="s" uri="/struts-tags"%&gt;</code>.
I fixed it by going to 'Project/MyEclipse/Web/Tag Libraries' and setting the Default TLD Prefix for Struts 1.2 Tiles Tags to 's'. I also had to do the same under 'Project/MyEclipse/Web/Configure workspace settings.../Tag Libraries'.

blocks|key|2459021|text|这是我的问题我是怎么解决的..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459022|我已经做了所有上面提到的事情，但是仍然会犯这个错误。原来我使用的是http://java.sun.com/jsp/jstl/fmt和http://java.sun.com/jsp/jstl/core的uri，这是不正确的。|offset|length|style|CODE|2459023|尝试将uris从上面切换到：|2459024|http://java.sun.com/jstl/fmt
http://java.sun.com/jstl/core|code-block|syntax|javascript|2459025|另外，确保在类路径中引用了正确的jars。|2459026|entityMap^0|0|X|W|1U|X|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

This was my problem and how I fixed it...

I had done everything everyone had mentioned above etc. but was still getting this error. Turns out I was using the uri's of <code>http://java.sun.com/jsp/jstl/fmt</code> and <code>http://java.sun.com/jsp/jstl/core</code> which were incorrect.

Try switching the uris from above to:

<pre><code>http://java.sun.com/jstl/fmt
http://java.sun.com/jstl/core
</code></pre>

Also, make sure you have the correct jars referenced in your class path.

blocks|key|997924|text|在Eclipse中，项目属性中的"Java模块依赖项“已被替换为"Deployment”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|997925|因此，为了用Eclipse解决这个问题，我的方法如下：|997926|右键单击中的项目并选择“Import.”|unordered-list-item|997927|接受默认选择“文件系统”并按下“下一步”|997928|按From目录行中的"Browse“键，转到tomcat安装并找到文件webapp/examples/WEB/lib(我有tomcat+6，其他版本的Tomcat可能有路径webapp/jsp-实例/WEB/lib)。一旦进入路径，按OK。|997929|单击“除了jstl.jar”和“standard.jar”以激活复选框|997930|在“进入文件夹”行上，单击“浏览”并选择“库”文件夹。我在项目中使用/lib。|997931|点击“完成”|997932|右键单击Package视图中的项目并选择属性(或按Alt+%2BEnter键)|997933|点击"Java构建路径“|997934|单击"Add“，单击您的项目，文件夹库，选择jstl.jar，按OK|997935|单击"Add“，单击您的项目，文件夹库，选择standard.jar，按OK|997936|按“确定”以关闭属性对话框|997937|单击Problems视图并选择消息"Classpath条目./jstl.jar将不会导出或发布。运行时ClassNotFoundExceptions可能会产生“。|997938|右击它并选择“快速修复”。|997939|接受默认的“将相关的原始类路径条目标记为发布/导出依赖项”并按Finish。|997940|对standard.jar也这样做|997941|这解决了问题，但是如果您想检查"Deployment“中发生了什么，请再次打开项目属性，选择"Deployment”，您将看到standard.jar和jstl.jar已经添加到WEB/lib文件夹中。|997942|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1E|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1F|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1G|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1I|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1K|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1L|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1M|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1N|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|F|7|1O|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|1P|8|@]|9|@]|A|$]]|$1|12|3|13|5|F|7|1Q|8|@]|9|@]|A|$]]|$1|14|3|15|5|F|7|1R|8|@]|9|@]|A|$]]|$1|16|3|17|5|F|7|1S|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|1T|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|1B|$]]

In Eclipse Helios "Java EE Module Dependencies" in the project properties has been replaced with "Deployment Assembly". 

So for solving this problem with Eclipse Helios, the way I did it is the following:

<ul>
<li>Right click on the project in package explorer and choose "Import..."</li>
<li>Accept the default selection "File System" and press "Next"</li>
<li>Press "Browse" in the From directory line, go to your tomcat installation and locate the file webapps/examples/WEB-INF/lib (I have tomcat 6, other versions of Tomcat may have the path webapps/jsp-examples/WEB-INF/lib). Once in the path press OK.</li>
<li>Click besides jstl.jar and standard.jar to activate the check boxes</li>
<li>On the line Into folder click on Browse and choose the library folder. I use /lib inside the project.</li>
<li>Click "Finish"</li>
<li>Right click on the project in Package Explorer view and choose properties (or press Alt + Enter)</li>
<li>Click on "Java Build Path" </li>
<li>Click "Add Jar", click on your project, folder lib, select jstl.jar, press OK</li>
<li>Click "Add Jar", click on your project, folder lib, select standard.jar, press OK</li>
<li>Press OK to dismiss the properties dialog</li>
<li>Click on the Problems view and select the message "Classpath entry .../jstl.jar will not be exported or published. Runtime ClassNotFoundExceptions may result.". </li>
<li>Right click on it and select "Quick Fix".</li>
<li>Accept the default "Mark the associated raw classpath entry as a publish/export dependency" and press Finish.</li>
<li>Do the same for standard.jar </li>
</ul>

This solves the problem, but if you want to check what has happened in "Deployment Assembly", open the project properties again, select "Deployment Assembly" and you'll see that standard.jar and jstl.jar have been added to WEB-INF/lib folder.

blocks|key|997394|text|检查F:\apache-tomcat-7.0.21\webapps\examples\WEB-INF\lib中的两个库|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|997395|jstl.jar|ordered-list-item|997396|standard.jar|997397|entityMap^0|2|1G|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|Q|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|L|$]]

Check the two libraries in <code>F:\apache-tomcat-7.0.21\webapps\examples\WEB-INF\lib</code>:

<ol>
<li>jstl.jar</li>
<li>standard.jar</li>
</ol>

blocks|key|997967|text|您只需进入构建路径->添加库，并为库类型添加选择“服务器运行时”。单击Next并选择一个服务器运行时来添加到类路径中，如果jstl.jar和standard.jar在您服务器的类路径中，问题就会消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|997968|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can simply go to Build Path -> Add Libraries and for the library type to add select "Server Runtime." Click Next and select a server runtime to add to the classpath and the problem goes away if jstl.jar and standard.jar are in your server's classpath.

blocks|key|933356|text|遇到同样的问题，我使用maven，所以我将其添加到我的web项目中的pom中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933357|<dependency>
++++<groupId>javax.servlet</groupId>
++++<artifactId>jstl</artifactId>
++++<version>1.2</version>+
++++<scope>provided</scope>
</dependency>|code-block|syntax|javascript|933358|这解决了问题，我使用了“提供”范围，因为和OP一样，所有东西都已经在JBoss中工作了。|933359|这里是我找到解决方案的地方：http://alfredjava.wordpress.com/2008/12/22/jstl-connot-resolved/|offset|length|933360|entityMap|0|LINK|mutability|MUTABLE|url|http://alfredjava.wordpress.com/2008/12/22/jstl-connot-resolved/^0|0|0|0|E|1S|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Ran into the same problem, I'm using maven so I added this to the pom in my web project:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.servlet&lt;/groupId&gt;
 &lt;artifactId&gt;jstl&lt;/artifactId&gt;
 &lt;version&gt;1.2&lt;/version&gt; &lt;!-- just used the latest version, make sure you use the one you need --&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

This fixed the problem and I used "provided" scope because like the OP, everything was already working in JBoss.

Here's where I found the solution: <a href="http://alfredjava.wordpress.com/2008/12/22/jstl-connot-resolved/">http://alfredjava.wordpress.com/2008/12/22/jstl-connot-resolved/</a>

blocks|key|933384|text|我也有同样的问题，一个条纹，标签库显示为找不到。我使用Indigo和Maven，当我选中Properties->Java+>Order&ExportTab(在一个新的项目签出上)时，我发现"Maven+Dependencies“复选框由于某种原因没有被选中。只需选中该框并执行Maven干净安装即可清除所有错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933385|我想知道为什么Eclipse不认为我希望构建路径中有我的Maven依赖项.|933386|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem with a stripes taglib uri showing as not found. I was using Indigo and Maven and when I checked Properties->Java Build Path->Order &amp; Export Tab I found (on a fresh project checkout) that the "Maven Dependencies" checkbox was unchecked for some reason. Simply checking that box and doing a Maven clean install cleared all the errors. 

I wonder why Eclipse doesn't assume I want my Maven dependencies in the build path...

blocks|key|2459276|text|我在STS+(suite工具源代码套件)上也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459277|在STS下，右键单击项目，超过“属性”、“项目方面”，而不是在窗口右侧单击“运行时”选项卡，并选中"VMware+vFabric+tc+Server+(.)“，然后单击"Apply”，刷新工作区后应该可以。|2459278|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem with STS (springtool source suite).

Under STS, right click on the project, than "Properties", "Project Facets", than on the right of the window click on the "runtime" tab, and check "VMware vFabric tc Server (...)", and click "Apply" and it should be OK after the workspace refresh.

blocks|key|997491|text|我在使用Tomcat6.0和Eclipse时遇到了同样的问题，我尝试了一些我朋友建议的东西，它对我很有用。我问的问题和我的答复的链接可以在这里找到：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|997492|JSTLTomcat6.0找不到taglib描述符错误|offset|length|997493|如果这解决了“找不到标签库描述符”的问题，请告诉我。|997494|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/10017956/jstl-tomcat-6-0-cannot-find-the-taglib-descriptor-error^0|0|0|R|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I was having the same problem using Tomcat 6.0 and Eclipse and I tried out something which my friend suggested and it worked for me.
The link for the question I asked and my reply commented can be found here:

<a href="https://stackoverflow.com/questions/10017956/jstl-tomcat-6-0-cannot-find-the-taglib-descriptor-error">JSTL Tomcat 6.0 Cannot find the taglib descriptor Error</a>

Let me know if this solves your "Cannot find the taglibrary descriptor" problem.

blocks|key|933496|text|我正在使用Spring插件和Spring模板项目。我必须先安装Maven+m2e插件：http://www.eclipse.org/m2e/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|933497|然后清理这个项目。在Project+->+Clean...下|style|CODE|933498|entityMap|0|LINK|mutability|MUTABLE|url|http://www.eclipse.org/m2e/^0|17|R|0|0|A|J|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

I'm using Spring STS plugin and a Spring webmvc template project. I had to install the Maven m2e plugin first: <a href="http://www.eclipse.org/m2e/" rel="nofollow">http://www.eclipse.org/m2e/</a>

And then clean the project. Under <code>Project -&gt; Clean...</code>

blocks|key|2459375|text|当我试图在JSP中包含JSTL核心库时：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459376|<%25@+taglib+prefix="c"+uri="http://java.sun.com/jsp/jstl/core"+%25>|code-block|syntax|javascript|2459377|在Eclipse+(Indigo)中我得到了以下错误：|2459378|Can+not+find+the+tag+library+descriptor+for+"http://java.sun.com/jsp/jstl/core"|2459379|我转到Properties+->目标运行时，然后检查我正在使用的服务器(Geronimo3.0)。大多数人都会使用Tomcat。这解决了我的问题。希望能帮上忙！|2459380|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

When I tried to include the JSTL Core Library in my JSP:

<pre><code>&lt;%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %&gt;
</code></pre>

I got the following error in Eclipse (Indigo):

<pre><code>Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"
</code></pre>

I went to the Project Properties -> Targeted Runtimes, and then checked the Server I was using (Geronimo 3.0). Most people would be using Tomcat. This solved my problem. Hope it helps!

blocks|key|933543|text|我也面临着同样的问题。这就是我为解决这个问题所做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933544|选择“项目”并右击。|ordered-list-item|933545|点击属性。|933546|单击“库”选项卡。|933547|点击‘添加罐子’。|933548|为您的错误添加相关jar。|933549|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

I faced same problem.
This is what I did to resolve the issue.

<ol>
<li>Select Project and right click.</li>
<li>Click on properties.</li>
<li>Click on libraries tab.</li>
<li>Click on 'Add Jars'.</li>
<li>Add relevant jar for your error.</li>
</ol>

blocks|key|933586|text|如果您的tld位于类路径(通常位于WEB目录下)，那么以下两个提示应该可以解决这个问题(不管您的环境设置如何)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933587|确保TLD中的<uri>与jsp页面的taglib指令中的uri匹配。tld的<uri>元素是标记库的唯一名称。|ordered-list-item|offset|length|style|CODE|933588|如果TLD没有<uri>元素，容器将尝试使用taglib指令中的uri属性作为到达实际tld的路径。例如，我可以在我的WEB文件夹中有一个自定义的tld文件，并使用这个tld的路径作为JSP中的uri值。然而，这是一个不好的做法，应该避免，因为路径将被硬编码。|933589|entityMap^0|0|7|5|13|5|0|7|5|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@$E|O|F|P|G|H]|$E|Q|F|R|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@$E|T|F|U|G|H]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|L|$]]

If your tld's are on the classpath, typically under the WEB-INF directory, the following two tips should resolve the issue (irrespective of your environment setup):

<ol>
<li>Ensure that the <code>&lt;uri&gt;</code> in the TLD and the uri in the taglib directive of your jsp pages match. The <code>&lt;uri&gt;</code> element of the tld is a unique name for the tag library.</li>
<li>If the tld does not have a <code>&lt;uri&gt;</code> element, the Container will attempt to use the uri attribute in the taglib directive as a path to the actual TLD. for e.g. I could have a custom tld file in my WEB-INF folder and use the path to the this tld as the uri value in my JSP. However, this is a bad practice and should be avoided since the paths would then be hardcoded.</li>
</ol>

blocks|key|998151|text|那么，您需要理解的是，总是有两件事，API和实现(请记住下面代码的分级格式)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|998152|compile+group:'javax.servlet.jsp.jstl',+name:'javax.servlet.jsp.jstl-api',+version:'1.2.1'|offset|length|style|CODE|998153|compile+group:'org.glassfish.web',+name:'javax.servlet.jsp.jstl',version:'1.2.1'|998154|因此，如果您使用的是一个没有jstl支持的servlet容器，那么当然它不会同时提供它们，我犯的一个错误是，我只将第一个放在其中，但是如果您使用的是完整堆栈应用服务器，即glassfish，那么glassfish就会将它们都包含在其中。|998155|entityMap^0|0|0|2I|0|0|28|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

well you need to understand there are always two things the API and the implementation (mind the gradle format of the following code)

<code>compile group:'javax.servlet.jsp.jstl', name:'javax.servlet.jsp.jstl-api', version:'1.2.1'</code>

<code>compile group:'org.glassfish.web', name:'javax.servlet.jsp.jstl',version:'1.2.1'</code>

so If you're using a servlet container with no jstl support then of course it will not provide both of them, a mistake which I made is that I only put the first one, but if you're using full stack application server i.e glassfish then glassfish will have both of them already inside.

blocks|key|997583|text|我也面临着同样的问题。确保在Eclipse和Tomcat工作目录中有相同版本的JSTL，即在\webapps\examples\WEB-INF\lib和lib文件夹中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|997584|entityMap^0|1A|T|24|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I also faced the same problem. Make sure you have same versions of JSTL in Eclipse and in the Tomcat work directory, i.e in <code>\webapps\examples\WEB-INF\lib</code> and in <code>lib</code> folder.

blocks|key|997593|text|对我来说，每当我尝试使用eclipse的新版本时，这个错误就会发生。显然，新的eclipse重置了M2_REPO变量，我在Marker视图中获得了所有标记库错误(有时带有Marker验证错误)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|997594|在更新M2_REPO变量以指向实际的maven存储库位置后，需要2-3项目->清洁迭代才能使一切正常工作。|997595|有时，除了这个标记库错误之外，还有一些xml验证错误(Ejb)。手动更新相应的XML文件，启动*.xsd文件查找，并解决xml验证错误。发布后，标签库错误也随之消失。|997596|entityMap^0|1D|7|1P|6|2D|6|0|3|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

For me, this error occurs whenever I try to use a new version of eclipse. Apparently, the new eclipse resets the <code>M2_REPO</code> variable and I get all the tag library error in the <code>Marker</code> view (sometimes with ejb validation errors).

After updating <code>M2_REPO</code> variable to point to actual maven repository location, it takes 2-3 Project -> Clean iterations to get everything working.

And sometimes, there are some xml validation errors(ejb) along with this tag library errors. Manually updating the corresponding XML file, initiates a *.xsd file lookup and the xml validations errors are resolved. Post this, the tag library errors also vanish.

blocks|key|2459539|text|另一方面，如果您只处理java源代码，并且从一个正在工作的大型项目中没有接触到这些错误，那么您可以直接关闭Eclipse中的验证。设置在首选项->Web->JSP文件->验证下|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459540|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

On the other hand, if you are only working on java source and are getting these errors from stuff you don't touch in a large project that is working, you can just turn off the validations in Eclipse. The settings are under Preferences->Web->JSP Files->Validation

blocks|key|933748|text|将jstl.jar替换为jstl1.2.jar解决了tomcat7.0的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|933749|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

replace jstl.jar to jstl1.2.jar resolved the issue for tomcat 7.0

blocks|key|2459635|text|此错误可能来自几个不同的来源。当Eclipse没有实现TLD文档中设置的JSP规范的版本时，就会发生一种情况(在对这个问题的其他回答中没有提到)。Eclipse版本在实现较新的servlet和JSP规范方面通常落后一年。例如，请参见这个Eclipse错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2459636|在这种情况下，您的web应用程序在Tomcat的最新版本中可能运行良好，但是Eclipse仍然可能会抱怨缺少TLD。短期解决方案(除了忽略Eclipse中的错误)是将JSP版本降低到Eclipse版本所支持的版本。|2459637|此外，请记住您正在实现的TLD版本。标记名从v1.1略有更改为v2.0+(即，info现在是taglib上的description，在tag下不是一个有效的元素，许多元素名称现在包含连字符)。Eclipse不允许拼写错误的TLD标记名。|style|CODE|2459638|TLD+2.0+(jsp-version+2.0)参考|2459639|TLD+2.1+(jsp-版本2.3)参考|2459640|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.eclipse.org/bugs/show_bug.cgi?id=473471|1|https://docs.oracle.com/cd/E12839_01/web.1111/e13722/tld.htm#TAGLB120|2|http://docs.oracle.com/javaee/5/tutorial/doc/bnamu.html^0|38|B|0|0|0|13|4|1A|6|1I|B|1V|3|0|0|R|1|0|0|L|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@$A|15|B|16|H|I]|$A|17|B|18|H|I]|$A|19|B|1A|H|I]|$A|1B|B|1C|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|L|3|M|5|6|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|N|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]|X|$5|Q|R|S|C|$T|Y]]]]

This error can arise from several different sources. One case (not mentioned in other answers to this question) occurs when Eclipse does not implement the version of the JSP specification set in the TLD document. Eclipse releases typically lag behind up to a year in implementing newer servlet and JSP specifications. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=473471" rel="nofollow noreferrer">this Eclipse bug</a> for example.

In this case, your web application may run fine in the latest version of Tomcat, but Eclipse may still complain about a missing TLD. The short term solution (short of ignoring the error in Eclipse) is to bump down the JSP version to the one that your version of Eclipse supports.

Also, keep in mind the TLD version you are implementing. The tag names have changed slightly from v1.1 to v2.0 (i.e., <code>info</code> is now <code>description</code> on <code>taglib</code> and is not a valid element under <code>tag</code>, many of the element names now contain a hyphen). Eclipse has no tolerance for misspelled TLD tag names.

<a href="https://docs.oracle.com/cd/E12839_01/web.1111/e13722/tld.htm#TAGLB120" rel="nofollow noreferrer">TLD 2.0 (jsp-version 2.0) Reference</a>

<a href="http://docs.oracle.com/javaee/5/tutorial/doc/bnamu.html" rel="nofollow noreferrer">TLD 2.1 (jsp-version 2.3) Reference</a>

I have a Java EE project which build fine with Ant, deploys perfectly to JBoss, and runs without any trouble. This project includes a few custom tag libraries (which is not <a href="https://stackoverflow.com/tags/jstl/info">JSTL</a>!), which are also working without any difficulties.

The problem is with the Eclipse IDE (Ganymede): in every single JSP file which uses our custom tags, the JSP parser flags the taglib include line with with this error:

<code>Cannot find the tag library descriptor for (example).tld</code>

This also causes every use of the tab library to be flagged as an error, and since the IDE doesn't have their definition, it can't check tag parameters, etc.

Our perfectly-working JSP files are a sea of red errors, and my eyes are beginning to burn.

How can I simply tell Eclipse, "The tag library descriptor you are looking for is "src/web/WEB-INF/(example)-taglib/(example).tld"?

I've already asked this question on the Eclipse support forums, with no helpful results.

Eclipse "cannot find the tag library descriptor" for custom tags (not JSTL!)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个Java项目，它使用Ant构建得很好，完美地部署到JBoss上，并且没有任何问题地运行。该项目包括一些自定义标记库(不是!)，它们也可以正常工作。问题在于Eclipse (Ganymede)：在使用我们的自定义标记的每个JSP文件中，JSP解析器用以下错误标记taglib包含行：Cannot find the ...

问Eclipse“找不到自定义标记的标记库描述符”(不是JSTL!)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse“找不到自定义标记的标记库描述符”(不是JSTL!)EN