|Resolving HTML, JSP, and XML Schema Problems [message #514059]
||Fri, 12 February 2010 10:39
Registered: January 2010
I'm trying to get my existing project loaded into Eclipse. I have a directory structure that looks something like this:|
I'm seeing the following three types of problems:
1. HTML Problems
Eclipse is complaining of bad HTML within my unit-test-data directory. I agree, the HTML is bad. However, it is what my app needs to deal with. How can I tell Eclipse to ignore anything in the unit-test-data directory? It wants to look at everything in the 'src' directory.
2. JSP Problem
In my .jsp files, I have:
<%@ taglib prefix"foo" tagdir="/WEB-INF/tags/foo" %>
Can not find the tag library descriptor for "/WEB-INF/tags/foo
How can I resolve this problem?
3. XML Schema Problems
In my WEB-INF directory I have web-app_2_5.xsd. Eclipse complains:
schema_reference.4: Failed to read schema document 'jsp_2_1.xsd', because...
src-resolve: Cannot resolve the name 'javaee:jsp-fileType' to a(n) 'type definition' component.
src-resolve: Cannot resolve the name 'javaee:jsp-configType' to a(n) 'type definition' component
I tried placing jsp_2_1.xsd in the directory, but that didn't help. How do I resolve these problems?
|Re: Resolving HTML, JSP, and XML Schema Problems [message #515072 is a reply to message #514059]
||Wed, 17 February 2010 15:56
|| Nitin Dahyabhai
Registered: July 2009
On 2/12/2010 5:39 AM, NC wrote:|
> I'm trying to get my existing project loaded into Eclipse. I have a
> directory structure that looks something like this:
> /web /META-INF
> /WEB-INF /tags
> I'm seeing the following three types of problems:
> 2. JSP Problem
> In my .jsp files, I have:
> <%@ taglib prefix"foo" tagdir="/WEB-INF/tags/foo" %>
> Eclipse complains:
> Can not find the tag library descriptor for "/WEB-INF/tags/foo
> How can I resolve this problem?
If you JSP files are not somewhere under the folder that directly
parents the WEB-INF folder, the JSP component looks to the flexible
layout support provided by the Module Core component in order to find
referenced resources. This usually starts with having the
org.eclipse.wst.common.modulecore.ModuleCoreNature nature on the project
and a .settings/org.eclipse.wst.common.component file detailing how the
project's contents would be assembled for deploying on the server.
WTP's web projects start out with this nature, and you may be able to
use one to help you author this file. I think 3.2 will have a user
interface to help with this, but don't hold me to that.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196177 may also be of
interest, as it sparked the JSP component's support for flexible layouts.
Eclipse WTP Source Editing
Eclipse WTP, IBM
Powered by FUDForum
. Page generated in 0.02153 seconds