For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 19 years, 10 months ago by
.
-
Posts
-
I’m having validation errors and unable to do “code complete” on the taglib names.
I have a fresh install of MyEclipse and Eclipse (see details below).
I created a web project.
Added Struts capabilities.
on the struts-config.xml visual editor, I created a “Standard JSP using Struts 1.2 with a form” (MyJsp.jsp).
Opened the file (MyJsp.jsp).
for every struts tag, I get the validation error:
taglib directive for “html” does not exist or TLD is not found.I modified none of the taglibs, web.xml, etc. However, even when I modify the URI of the taglib, I still can’t get it to see it. Everything appears to be in the right locations (i.e. the MyEclipse wizards seemed to work correctly). But the end result is the JSP compiler/validator doesn’t recognize the struts taglibs.
I hope someone can help. Thanks!
===========================
– System Setup ——————————-
Operating System and version: XP
Eclipse version: 3.2.0
Eclipse build id: org.eclipse.platform
MyEclipse Enterprise Workbench v5.0.1GA
20060810-5.0.1-GAFresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: Yoxos (and a few others)
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 2
MyEclipse version: 5.0.1 GA
Eclipse JDK version: 1.4.2
Application Server JDK version:
Are there any exceptions in the Eclipse log file? where is the file?If this is a DB related question please answer the following:
– Message Body ——————————-
I have a feeling you added Struts 1.1 capabilities to your project but are trying to use the Struts 1.2 template… can you check your project properties under MyEclipse > Struts?
it is struts 1.2. but good news…
ok… i reinstalled everything. but, made sure it was 3.2.0 base eclipse with nothing else (no plugins). the jdk was 1.4.2_2 — so, I took it to 1.4.2_7. Anyway, after doing so, I was able to get it all to work this morning. yeah!
