|Re: [wtp-dev] Content assist behaving oddly for JSPs|
> I can say that the embedded Java content assist won't work unless > you have the Servlet API on the Java Build Path somehow, and it can > be quirky in cases where no Java Source Folder is set on the project I do have the servlet api on the classpath (from JBoss4.0.3 which we are still stuck on), and content assist does work on new JSP files, just not in existing ones BUT if you open an existing JSP that isn't working with content assist, and re-save it using "save as", content assist works from that point onwards. (save doesn't work, it has to be "save as" and overwrite the original file). This is a good enough work around for now, but does this mean there is some metadata or cache that is being updated by "save as" that isn't changed by save? << JOC >> -- View this message in context: http://www.nabble.com/Content-assist-behaving-oddly-for-JSPs-tp24252444p24303076.html Sent from the Eclipse WTP - general mailing list archive at Nabble.com.
Back to the top