[Paul Stanton]

3. @support-rkalla wrote:

Yes it is, and it is marked as such

yes, but it wouldn’t be marked if you went and put a space between “<jsp:f” and “orward”

4. fair enough ..wasn’t what i expected but fair enough.

5. ok .. look forward too it .. thats plagued me for ages.

NOW
the original problem has re-occurred for a new tag 🙁

Unable to find setter method for attribute: pageIdProp

and the jsp runs as expected on the app server.

Thanks for your help guys .. sorry if i sound frustrated .. just trying to be quik.

[Paul Stanton]

this still happens .. old tag, new attribute :: jsp compiles fine on tomcat with same tld and tag .class, but in eclipse/myeclipse jsp editor shows an error: “unable to find setter method for attribute: xxxx”

[Riyad Kalla]

pstanton,
It’s possiblet he taglib cache is out of sync, try rebuilding your project and reloading MyEclipse.

[Paul Stanton]

the ‘remove all validation markers’ hack does not work, ‘clean working set’ seems to have (either that or touching the tld repeatedly)…
can you log a bug re the cache getting out of sync please, it should not happen.

thanks.

[Riyad Kalla]

Bug logged, sorry for the trouble.

[Paul Stanton]

no worries .. btw for others with this issue, the secret is you need to ‘clean’ AND ‘remove validation markers’

[Author]

Posts