[Ensonik]

I’m getting a lot of the following since I upgraded to the latest version of MyEclipse (downloaded today off your site):

<3>Validation error messages from TagLibraryValidator for c</h3><p>null: java.lang.IllegalStateException: can’t declare any more prefixes in this context</p><h3>Validation error messages from TagLibraryValidator for fmt</h3><p>null: java.lang.IllegalStateException: can’t declare any more prefixes in this context</p>. NOTE: No JSP line number was avaliable so line 1 was used for the marker.

I’m running on Eclipse 3.0.

Not sure what’s up. Any ideas?

[Riyad Kalla]

What is your Build ID for Eclipse? (Help > About)

Also what does the page look like giving you those problems? I am not farmiliar with this problem…

[Ensonik]

The build is:
Version: 3.0.0
Build id: 200406251208

The problem is showing up on all the JSP’s where I’ve got:
<%@ taglib uri=”/WEB-INF/c.tld” prefix=”c” %>

The page loads up fine in a browser, it just gives me all these hundreds of annoying errors in the workbench.

[Riyad Kalla]

Ensonik,
Do you have web.xml entries mapping that URI to your c.tld file? Please note that your taglib URI is an identifier, its not a path. You happen to have typed an absolute path into the field, but ME/App Server only uses that value as a unique identifier to lookup the *actual* location via your web.xml file or via TLD files contained in JAR files in your build path.

You could just as easily change the URI value to:
uri=”hamsandwich/with/cheese”

and as long as you had <taglib> entries in your web.xml file mapping your /WEB-INF/c.tld file to the URI “hamsandwich/with/cheese”, then you are fine.

While this page might work fine in Tomcat or another app server, ME has to follow the spec and enforce what it says, because your page may not work in another app server (WebLogic, Resin, Webspehere, etc.)

[Author]

Posts