Yes, I am using the WTP plug-in and the project is a Web Application. I am not using maven to build Eclipse... I am using the canned Eclipse 3.2.1 from eclipse.org and all the latest plug-ins downloaded from inside Eclipse.
I also found a note at the bottom of section 2 of http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 that seems to confirm the need for the baind-aid - see "usefull for some IDE's" comment there. (An alternative is specified in 5.4 as suggested by Levan, but it makes the app - which could be an intranet app - dependent on a connection to the internet, not good for mission-critical apps) -----Original Message----- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Monday, November 13, 2006 1:56 PM To: Struts Users Mailing List Subject: Re: Struts 1.3.5 and Eclipse 3.2 I hope you meant Eclipse *Web Tools* and that your project is a Web Application. If not, then Eclipse (as Robin hints at below) has no concept of the web root or what jars belong where and why. That's the purpose of having a project type that understands Web Applications. If using Maven, to generate the appropriate Eclipse config files for your project, try this... $ mvn eclipse:eclipse -Dwtpversion=1.0 -- James Mitchell 678.910.8017 On Nov 13, 2006, at 1:11 PM, Bruno Melloni wrote: > I did some testing and came to the conclusions below. I might be > wrong, but I think these are correct: > > - Eclipse 3.2 (plus plug-ins) is not yet compatible with Struts 1.3.x. > Chances are that it is also incompatible with Struts 2.0.x. > - Struts 1.3.x has changed how TLD tags are placed on the project > structure. > - The Struts 1.3.x approach seems to be to supply them inside > struts-taglib-1.3.5.jar, and to access them through the classpath in > /META-INF/tld. > - The Struts 1.3.x approach should not cause problems when executing > the application, but is a nuisance in the Eclipse Editor. > - The old 1.2.x approach of placing the TLDs in /WEB-INF is still > usable. > - The Eclipse 3.2 editor will only recognize tags placed in /WEB-INF. > > So... > > Band-aid solution: > - Extract TLD files from struts-taglib-1.3.5.jar into the /WEB-INF > folder > - Use the old URI: "/WEB-INF/<whicheverTag>.tld" > > Real solution: > - Eclipse 3.2 needs a bug-fix. It should be reading the URI, and not > rely on a specific location. > > Bruno > > -----Original Message----- > From: robin bajaj [mailto:[EMAIL PROTECTED] > Sent: Friday, November 10, 2006 4:12 PM > To: Struts Users Mailing List > Subject: Re: Struts 1.3.5 and Eclipse 3.2 > > 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]
