- This topic has 2 replies, 2 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
IWAE0010E Run-time exception java.lang.VerifyError occurred during validation. The validator being run was JSP Validator and the message thrown was (class: ex.ThumbnailIterationAction, method: getImageHref signature: ()Lorg/jdom/Element;) Incompatible argument to function.That method’s signature is pretty simple: “private Element getImageHref()” I’ve even changed that to void, but for some reason MyEclipse still wants to think that it returns an Element and produces that warning.
This class extends LoopTagSupport and so I have it defined in my own .tld file. MyEclipse is also complaining about it not being a valid XML file, but I have the required tlibversion, shortname, and a tag along with the optional uri, jspversion and info.
This is my first attempt at a custom tag so its likely I’ve done something wrong. Eclipse 3.0.1 MyEclipse 3.8.3
cwilkes,
When developing custom taglibs ME is a bit overzealous with the caching of the TLD data at times, unfortunately the only workaround I Have found is to close the project, restart MyEclipse open and rebuild the project. I know this is a PIA and am currently talking with the devs to see if we can get this fixed.I’m not sure what you mean by “rebuild the project” — I did a “Run Validation” and it cleared up a lot of the errors, one of the several VerifyError mesages that reference the org.jdom.Element are still there.
I also have the Spring Eclipse plugin http://springframework.sourceforge.net/spring-ide/eclipse/ which sometimes also prints out warnings about missing files I’ve taken out of its configuration. I bring this up as the Run Validation cleared out those errors.
