Well, one more thing that may or may not be the reason Eclipse is
complaining.
The taglib jar file (with embedded tlds) must be on the classpath of
the project, which MyEclipse, Nitrox, and a few others (IBM RAD) will
force upon you if the jar is under WEB-INF/lib. When I say "force",
I mean, if you drop the jar under WEB-INF/lib from the file system
(Windows Explorer, Finder, whatever), then go back to eclipse and
refresh the project, those IDEs I mentioned will see the new jar and
add it to the classpath and deployment path.
If a project truly is a "Dynamic Web Project" in the way that Web
Tools defines them, then the taglib URIs should resolve fine.
Hope that helps.
--
James Mitchell
678.910.8017
On Nov 14, 2006, at 11:21 AM, Bruno Melloni wrote:
I think I am being misunderstood.
The problem is not related to building a WAR/EAR and running on an
application server. Using the TLDs from the jars nor using the URI
(thanks for the clarification Wendy) are fine for running in an
application server.
The problem is the annoying error message from the Eclipse editor. It
is the Eclipse editor (or the WTP plug-in) that is not smart enough to
recognize the taglibs unless they are physically in WEB-INF.
From the messages in this thread that does not appear to be a problem
with the pre-packaged MyEclipse distribution, but it does affect the
vanilla Eclipse + manually added plugins - even if they are the latest
versions. Hopefully this problem will go away in a future version of
Eclipse and the WTP. Maybe they'll copy the MyEclipse solution,
and if
I understood James' comment correctly, it might just be a question
of a
simple rebuild.
bruno
-----Original Message-----
From: Ed Griebel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 9:54 AM
To: Struts Users Mailing List
Subject: Re: Struts 1.3.5 and Eclipse 3.2
YOu don't need to (and never should) extract TLD files from jars
and put
them into a WEB-INF directory in your war. Web app servers that follow
servlet version 2.3 and up have been able to extract TLDs from jars.
See for more information:
http://struts.apache.org/1.2.9/userGuide/
configuration.html#dd_config_ta
glib_23
-ed
On 11/10/06, robin bajaj <[EMAIL PROTECTED]> wrote:
Or actually you can just get it from your project structure,
depending
upon your jsp and tld location.
Say your jsp is in WebRoot/ [[ webRoot/abc.jsp ]]
and your tld is lying in web-Inf/struts-logic.tld {usual tooling/
user
practice}
Then you can access the .tld as
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
I wonder why you dont have the actual .tld files in the web-inf
folder
of your webApp. If you actually don't then you can get them from
Struts download site.
Hope it helps,
regards,
robin
Paul Benedict wrote:
The taglib URI should be the the http:// address, not the /META-INF
location. If you are unsure what the address is, open up the TLD
files and see.
-- Paul
Bruno Melloni wrote:
I have a strange problem, with Struts 1.3.5 in Eclipse 3.2.
- struts-taglib-1.3.5.jar is in the classpath.
- Inside the jar, in /META-INF/tld are the struts tld files. - I
have the following in index.jsp:
<%@ taglib uri="/META-INF/tld/struts-logic.tld" prefix="logic"
%>
<logic:redirect forward="welcome" />
- Eclipse whines about the tag not being known. I even tried
replacing the URI with "http://struts.apache.org/tags-logic";, but
no cigar.
Any idea what is going on, and how to fix it?
Thanks,
Bruno
-------------------------------------------------------------------
-- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
