blocks|key|3028799|text|检查.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/Myproject/WEB-INF/lib/standard-1.1.2.jar是否已损坏(如果需要，请执行一些清理操作)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3028800|entityMap^0|2|2V|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Check that 
<code>.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/Myproject/WEB-INF/lib/standard-1.1.2.jar</code> is not corrupted (and do some cleanup if required).

blocks|key|300265|text|看起来maven/m2eclipse插件有问题。就连我也看到了同样的问题。默认情况下，它会将所有jar文件推送到服务器lib目录。其中包括作用域“提供的”jar文件。此问题已在旧版本的m2eclipse中修复。但它似乎又被引入了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300266|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|$]]

It looks like there is an issue with maven/m2eclipse plugin. Even I am seeing the same issue. By default it is pushing all the jar files to server lib directory. Which includes the scope "provided" jar files. This issue was fixed in old versions of m2eclipse. But it got introduced again it seems.

blocks|key|303129|text|删除：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303130|++javax.servlet.jsp+++++jsp-api+++++2.0++++provided++|code-block|syntax|javascript|303131|从你的pom.xml和这应该做的..它在我的案例中起作用了:-)|303132|entityMap^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|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

remove :
 
 javax.servlet.jsp 
 jsp-api 
 2.0
 provided
 

from you pom.xml and that should do.. it worked in my case :-)

blocks|key|3028936|text|在我使用Indigo+Eclipse3.7移动并进行了m2e的最新更新后，这个问题发生在我身上，我删除了下面的依赖项，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3028937|<dependency>
++<groupId>javax.servlet.jsp</groupId>
++<artifactId>jsp-api</artifactId>
++<version>2.1</version>
++<scope>provided</scope>
</dependency>|code-block|syntax|javascript|3028938|我不确定为什么这些问题消失了，因为据我所知，新版本的m2e已经有了jsp编译库。|3028939|entityMap^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|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

After i moved using Indigo Eclipse 3.7 and took the lasted update of m2e, this problem happened to me, i remove the dependency below it worked well.

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.servlet.jsp&lt;/groupId&gt;
 &lt;artifactId&gt;jsp-api&lt;/artifactId&gt;
 &lt;version&gt;2.1&lt;/version&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

I'm not sure why the issues was gone, as my understanding new version of m2e has jsp compilation library already.

blocks|key|298034|text|平台:+eclipse+3.7+indigo，tomcat+6.0.29|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298035|注释掉了pom.xml中的以下依赖项：|298036|javax.servlet++
org.apache.taglibs++|code-block|syntax|javascript|298037|这解决了这个问题(因为它们是通过tomcat提供的)……|298038|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

platform: eclipse 3.7 indigo, tomcat 6.0.29 
commented out the following dependencies in pom.xml: 

<pre><code>javax.servlet 
org.apache.taglibs 
</code></pre>

this cleared up the issue (as they are provided via tomcat) ...

blocks|key|3243304|text|我同意Jay的回答。我这里也有同样的问题。如果从pom.xlm中删除jsp-api，maven测试将失败，因为它在jsp-api+jar中找不到jspWriter类。如果我将jsp-api保存在pom中，并将其设置为'provided‘或'test'，那么Tomcat端将会失败，因为m2e插件会将jsp-api+jar推送到maven依赖项中，然后将其包含在我部署的tomcat库中。我会说这是插件问题，因为jsp-api必须在pom.xml中声明，因为它是由应用服务器提供的。我找不到任何方法来解决这个问题，只能在每次tomcat服务器同步后手动删除jsp-api。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3243305|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|$]]

I agree with Jay's answer. I have same issue here. If I remove jsp-api from pom.xlm, maven test will fail because it cannot find jspWriter class in jsp-api jar. If I keep jsp-api in pom and set it to 'provided' or 'test', tomcat side will fail as the m2e plugin pushes jsp-api jar to maven dependencies which is then included in my tomcat deployed lib. I would say it's plugin issue as jsp-api has to be declared in pom.xml as provided because it is provided by application servers.
I can't find any way of solving this issue but to manually delete the jsp-api every time after tomcat server synch.

blocks|key|298061|text|与Eclipse，请确保您安装了'Maven+Integration+for+EclipseWebApi.jar‘和其他插件，没有，Eclipse更改您的类路径并在您的WTP应用程序中包含servlet-api.jar。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|298062|entityMap^0|1T|19|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

With Eclipse, please assure that you installed 'Maven Integration for Eclipse WTP '
With the other plugin without WTP, eclipse change your classpath and include servlet-api.jar in your webapps.

blocks|key|300444|text|快速修复：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|300445|备份.classpath和.project以及.settings/org.eclipse.wst.common.component。|300446|运行以下命令：|300447|mvn+eclipse:eclipse|code-block|syntax|javascript|300448|或者，右键单击项目上的，在Maven子菜单中，您可以使用Update+Project...命令，我认为该命令具有相同的功能。|300449|重新发布。|300450|说明：|300451|您可能将所有Maven依赖项作为部署程序集添加到您的项目中。这会将所有Maven类路径条目复制到WEB-INF/lib目录。打开您的.classpath文件(在项目的根目录下)，您可能会找到以下XML：|300452|<classpathentry+kind="con"+path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER">
++++<attributes>
++++++++<attribute+name="org.eclipse.jst.component.dependency"+value="/WEB-INF/lib"/>
++++</attributes>
</classpathentry>|300453|这意味着复制每个.jar文件，这在本例中成为一个问题。|300454|更新项目应该删除上面的XML块，并显式列出JAR文件。|300455|因此，如果您重新打开.classpath，您将看到以下内容：|300456|<classpathentry+kind="var"+path="M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1.jar"+sourcepath="M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1-sources.jar"/>
<classpathentry+kind="var"+path="M2_REPO/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar"+sourcepath="M2_REPO/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1-sources.jar"/>
...|300457|这是您仍然需要的类路径，但它删除了将它们复制到lib的依赖关系。相反，如果打开.settings/org.eclipse.wst.common.component/，您将看到JAR文件现在显式列出：|300458|<dependent-module+deploy-path="/WEB-INF/lib"+handle="module:/classpath/var/M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1.jar">
++<dependency-type>uses</dependency-type>
</dependent-module>|300459|而且，您会注意到jsp-api-2.1.jar现在丢失了。将相同的逻辑应用于其他JAR文件。|300460|有没有人知道如何让这一切自动进行？|300461|entityMap^0|0|5|0|0|0|0|D|5|S|H|0|0|0|3|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1J|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1K|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1L|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1R|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1V|8|@]|D|@]|E|$]]|$1|W|3|X|5|L|7|1W|8|@]|D|@]|E|$M|N]]|$1|Y|3|Z|5|6|7|1X|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|14|3|15|5|L|7|20|8|@]|D|@]|E|$M|N]]|$1|16|3|17|5|6|7|21|8|@]|D|@]|E|$]]|$1|18|3|19|5|L|7|22|8|@]|D|@]|E|$M|N]]|$1|1A|3|1B|5|6|7|23|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|24|8|@]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|1F|$]]

Quickfix:

Make a backup of .classpath and .project and .settings/org.eclipse.wst.common.component.

Run this command:

<pre><code>mvn eclipse:eclipse
</code></pre>

Or, right-click over the project, in the Maven sub-menu, you have an Update Project... command which I think does the same thing.

Republish.

Explanation:

You likely added all Maven Dependencies as a Deployment Assembly to your project. This copies all Maven class path entries to the WEB-INF/lib directory. Open your .classpath file (at the root of your project) and you'll probably find the following XML:

<pre><code>&lt;classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"&gt;
 &lt;attributes&gt;
 &lt;attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/&gt;
 &lt;/attributes&gt;
&lt;/classpathentry&gt;
</code></pre>

That means copy EVERY .jar file which becomes a problem in this case.

Updating the project should remove the XML block above and explicitly list the JAR files.

So, if you re-open .classpath, you'll see this instead:

<pre><code>&lt;classpathentry kind="var" path="M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1.jar" sourcepath="M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1-sources.jar"/&gt;
&lt;classpathentry kind="var" path="M2_REPO/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar" sourcepath="M2_REPO/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1-sources.jar"/&gt;
...
</code></pre>

This is for the classpath which you still need, but it removed the dependency to copy them to lib. Instead, if you open .settings/org.eclipse.wst.common.component/, you'll see that the JAR files are now explicitly listed:

<pre><code>&lt;dependent-module deploy-path="/WEB-INF/lib" handle="module:/classpath/var/M2_REPO/com/google/code/gson/gson/2.2.1/gson-2.2.1.jar"&gt;
 &lt;dependency-type&gt;uses&lt;/dependency-type&gt;
&lt;/dependent-module&gt;
</code></pre>

And, you'll note that jsp-api-2.1.jar is now missing. Apply the same logic to the other JAR files.

Does anyone know how to make this automatic?

blocks|key|3243396|text|您必须从pom.xml中的jstl导入中排除jsp-api依赖：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3243397|<dependency>
++++<groupId>javax.servlet.jsp.jstl</groupId>
++++<artifactId>jstl-api</artifactId>
++++<version>1.2</version>
++++<exclusions>
++++++++<exclusion>
++++++++++++<groupId>javax.servlet</groupId>
++++++++++++<artifactId>servlet-api</artifactId>
++++++++</exclusion>
++++++++<exclusion>
++++++++++++<artifactId>jsp-api</artifactId>
++++++++++++<groupId>javax.servlet.jsp</groupId>
++++++++</exclusion>
++++</exclusions>
</dependency>|code-block|syntax|javascript|3243398|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You must exclude jsp-api dependency from jstl import in your pom.xml :

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.servlet.jsp.jstl&lt;/groupId&gt;
 &lt;artifactId&gt;jstl-api&lt;/artifactId&gt;
 &lt;version&gt;1.2&lt;/version&gt;
 &lt;exclusions&gt;
 &lt;exclusion&gt;
 &lt;groupId&gt;javax.servlet&lt;/groupId&gt;
 &lt;artifactId&gt;servlet-api&lt;/artifactId&gt;
 &lt;/exclusion&gt;
 &lt;exclusion&gt;
 &lt;artifactId&gt;jsp-api&lt;/artifactId&gt;
 &lt;groupId&gt;javax.servlet.jsp&lt;/groupId&gt;
 &lt;/exclusion&gt;
 &lt;/exclusions&gt;
&lt;/dependency&gt;
</code></pre>

blocks|key|3029192|text|从.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/Myproject/WEB-INF/lib/中删除了jsp-api+2.0，这对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3029193|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|$]]

Removed jsp-api 2.0 from 
.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/Myproject/WEB-INF/lib/
this worked for me .

blocks|key|3029209|text|我在netbeans+IDE+8.0.2中也遇到了同样的错误。事实证明，我的部分设置为8080，用于传出和关闭。我将Tomcat服务器的输出更改为8081。啊，真灵!然后我更改了我的关闭端口8005。要更改，请转到Tools>Servers>|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3029210|我的tomcat服务器现在可以工作了。|3029211|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 was getting the same error in netbeans IDE 8.0.2. It turns out my part was set to 8080 for outgoing and shutdown. I changed the outgoing to 8081 for Tomcat server. It worked! I then changed my shutdown port 8005. To change go to Tools>Servers> 

My tomcat server now works.

there's this issue with JSTL I'm stuck with for the past couple of days. Any help is appreciated.

Tomcat 6.0.28 
Eclipse: Helios

pom.xml :

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;javax.servlet&lt;/groupId&gt;
 &lt;artifactId&gt;jstl&lt;/artifactId&gt;
 &lt;version&gt;1.1.2&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;javax.servlet&lt;/groupId&gt;
 &lt;artifactId&gt;servlet-api&lt;/artifactId&gt;
 &lt;version&gt;2.4&lt;/version&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt; 
 &lt;groupId&gt;taglibs&lt;/groupId&gt; 
 &lt;artifactId&gt;standard&lt;/artifactId&gt; 
 &lt;version&gt;1.1.2&lt;/version&gt; 
&lt;/dependency&gt;
&lt;dependency&gt; 
 &lt;groupId&gt;javax.servlet.jsp&lt;/groupId&gt; 
 &lt;artifactId&gt;jsp-api&lt;/artifactId&gt; 
 &lt;version&gt;2.0&lt;/version&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

JSP:

<pre><code>&lt;%@ page session="true"%&gt;
&lt;%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %&gt;
&lt;%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %&gt;
&lt;%@ taglib prefix="utilfn" uri="/utility-functions" %&gt;
</code></pre>

web.xml:

<pre><code>&lt;web-app id="WebApp_ID" version="2.4" 
 xmlns="http://java.sun.com/xml/ns/j2ee" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee 
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"&gt;
</code></pre>

When I deploy the Maven-built war on tomcat 6 using the manager it works fine. 
When I run it as "Run As > Run On Server" inside eclipse, I get this:

<blockquote>
 Unable to read TLD "META-INF/c.tld" from JAR file "file:/&lt;- location ->/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/Myproject/WEB-INF/lib/standard-1.1.2.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlCoreTLV
</blockquote>

Wherever I look, it says the same thing:

<blockquote>
 <ol>
 <li>Make sure servlet-api and jsp-api are not in lib</li>
 <li>Make sure to use the right JSTL version and URI that goes with JSP 2.0.</li>
 </ol>
</blockquote>

And they seem to be fine as I can deploy the war independently. So what's wrong here!?

Unable to read TLD "META-INF/c.tld"

服务器

Eclipse

在过去的几天里，我一直在处理JSTL的这个问题。任何帮助都是非常感谢的。Tomcat 6.0.28Eclipse: Heliospom.xml： <dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> <vers...

问无法读取TLD "META-INF/c.tld“
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法读取TLD "META-INF/c.tld“EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法读取TLD "META-INF/c.tld“
EN