>> The problem is that the WTp JSP validator issues an error with "foo can
>> not be resolved".
> I have this same problem, its with a custom tag I wrote my own, but it
> actually is with any tag.
> Example, of my JSP:
> <dh:mytag id="myvar" .../>
> then in my JSP after the tag I put the snippet
> <%= myvar %>
> the code actually WORKS, but the JSP editor in eclipse says theres an error:
> cannot resolve "myvar"
In both of these cases a TagExtraInfo class needs to be declared
that returns information stating that the id/name attributes end up
creating local Java variables along with the correct scopes. The
JSP editor will attempt to load that class and talk to it, but it
has limitations when doing so, among them that the VM running
Eclipse must be able to read the class file--no running Eclipse with
1.4 and using a tag library compiled for 1.5.
Structured Source Editor
Eclipse WTP, IBM Emerging Technologies
Giovanni P. wrote:
> I doesnt depend on the JVM version.
> I tested this on another IDE with JVM 1.4 and it works correctly.
> I think it's some sort of bug or misconfiguration of Eclipse WTP.
Actually, in WTP it does depend on the JVM version somewhat--I can't
tell you how other IDEs manage it. Glamoute, is your project's
directory directly under the workspace folder or is it elsewhere?
You might be affected by bug 178443.