- This topic has 15 replies, 5 voices, and was last updated 12 years, 6 months ago by
.
-
Posts
-
MyEclipse Enterprise Workbench
Version: 10.0
Build id: 10.0-20111028On opening an existing JSP page I see several of these warnings:
NLS missing message: Obsolete_attribute_name___ERROR_ in: org.eclipse.wst.html.core.internal.HTMLCorePluginResourcesIs there a way to get rid of these messages or to fix it?
Thanks,
BijuBiju,
The warning messages can be ignored.
Can you please copy paste the contents of the myeclipse.ini file for us to take a look ? The myeclipse.ini file can be found in the same folder as your MyEclipse executable. Open it in any text editor and paste the contents here.
Hello:
While I know these can be ignored, these are interspersed with the other warnings that I would like to address. However there are so many of these in the JSP that it becomes a “needle in the haystack” situation.
Attached is the INI file:
—————————————————–
#utf8 (do not remove)
#utf8 (do not remove)
-startup
../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
–launcher.library
../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700
-install
C:\MyEclipse\MyEclipse 10
-vm
C:\MyEclipse\Common\binary\com.sun.java.jdk.win32.x86_64_1.6.0.013\bin\javaw.exe
-configuration
C:\MyEclipse\MyEclipse 10\configuration
-vmargs
-Xmx2048m
-XX:MaxPermSize=512m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignoreBiju,
Thank you for the details.
1) Can you please take a look at this thread,try the suggestion and check if the issue persists ?
http://stackoverflow.com/questions/7546219/nls-missing-message-cannot-find-facelet-taglib2) If you are still seeing the issue, please send us the .log file which is located at <workspace dir>/.metadata/.log for us to investigate further.
Swapna:
I tried each of the options below:
Close/reopen project.
Rightclick project > Validate.
Project > Clean… and clean selected project.
Restart Eclipse.However, none of these steps helped in alleviating the issue.
I am attaching the log file with filename/extension changed as requested by you.Thanks,
BijuBiju,
Thanks for the log file. However, I can see no entries about NLS missing messages. We have traced a problem with the error message that you reported in your opening post, and have raised a bug report for it. Are all of the “NLS missing message” messages exactly the same? If there are others, we’d like to trace the cause of those also. If there are other such messages, can you clear the log file then replicate the problem that produces those messages and attach that log file?
Sorry for the inconvenience.
Tony:
I checked the project and logs and did not see any other NLS warning messages.
I will update this post if I find any.Thanks,
BijuHere’s the log after I faced another issue while saving a change on a JSP.
Hope this helps as well!Thanks,
BijuBiju,
Thanks for the log file but I’m not sure what problem this is related to. If you are not seeing a problem in your use of MyEclipse, then you can disregard the errors. If you are seeing a problem, please provide more details, including screenshots, if appropriate.
Biju,
I am not sure if you got a resolution to your issue or not. I also encountered similar issue when I upgraded to 10.x.
Looks like, 10.x JSP editor treats each JSP as HTML5 (for HTML content) and most of the attributes, you see the NLS missing error, are no longer valid in HTML 5.
if you add the following in the beginning of JSP page then all of your NLS warnings will vanish.
<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>
In my case , i can’t do as there are plenty of JSPs and they are included into another main JSPs.
I could not get any solution for that. I got to leave with the warnings in my JSP.
regards
RajuI am also having this issue.
I have hundreds of jsp pages that do not have a DOCTYPE tag because they are included by other pages.
We need a new setting to specify the default HTML DOCTYPE for a project. This would be a very welcome addition.
havoc77,
Sorry you are seeing this problem.
I have raised an enhancement request to get something into the next release, though that can’t be guaranteed.
There is also an existing bug report for the incorrect message being issued, which should be fixed in the next release.
In the meantime, you can turn off JSP Content validation by right clicking on the project, selecting MyEclipse->Manage Validation, selecting “Enable project specific settings” and then deselecting the JSP Content Validator, for both manual and build. You may need to run validation manually and/or close and open the project to have previous validation markers cleaned up.
I hope this helps.
Problem Solved!!!
This feature already exists.
Go in to the properties for a web project, and go to Web Content Settings (See attachment)
From here you can select the default DOCTYPE for where no DOCTYPE is declared, and can also select the default CSS level to validate against.
I hope this helps the previous posters.
