- This topic has 3 replies, 2 voices, and was last updated 21 years ago by Scott Anderson.
-
AuthorPosts
-
Riyad KallaMemberI just ran across this because my tag lines were too long and I didn’t noticed I had duplicate attributes in them. ME described the error as “unexpected blah=…” where blah is the name of the attribute. It took me quite a while to figure out it meant duplicate. If this isn’t hard to change, that’d be great if it could report two separate conditions. If its a PIA just close the request, its not too big. (just spit and polish)
Scott AndersonParticipantIf this isn’t hard to change, that’d be great if it could report two separate conditions. If its a PIA just close the request, its not too big.
It’s actually a PIA because the error message and line to attribute it to comes from Xerces. We really just take it and mark it. 🙂
Of course, XML code assist shouldn’t volunteer an attribute if you’ve already used it within the tag. Did it?
–Scott
MyEclipse Support
Riyad KallaMember1) If its a PIA then scrap it, no need to waste your time on such a minor thing.
2) Actually yea the code complete did, the tag in question was:
<html:image src=”blah” border=”0″ value=”yakkity” border=”0″ />well it was a lot longer than that, but the problme was that I didn’t see the “Border” attribute at the end, so I added it manually at the beginning. When that line kept comming up with an error after I addeed border, I removed my border and hit autocomplete, and it gave me the border completion as an option. So I put it back in and saw the error. So then I maximized my editor screen and saw all the sudden at the end of the line that I already had the border attribute. At which point I remove the dupe.
But to make a long story short, the autcomplete suggested border to me… its trying to trick me! 8*)
Scott AndersonParticipantBut to make a long story short, the autcomplete suggested border to me… its trying to trick me! 8*)
Ah, that’s because the code completion engine limits the assist proposals by looking at the attributes already associated with the element. However, it may have missed attributes defined subsequently to the current edit position, especially if there is some sort of error in the file structure after that.
–Scott
MyEclipse Support -
AuthorPosts