Eclipse validating xhtml slow

XXMax Perm Size 256M -showsplash org.eclipse.platform –launcher.

XXMax Perm Size 256m –launcher.default Action open File -vmargs -server -Dosgi.required Java Version=1.5 -Xmn128m -Xms1024m -Xmx1024m -Xss2m -XX: Perm Size=128m -XX: Max Perm Size=128m -XX:+Use Parallel GC 4. Then set the Im Disk driver to auto-load at Command Prompt with administrative privileges (for example right-click, start as Administrator), type: sc config imdisk start= auto net start imdisk create a 200m ram disk as driver n by: imdisk -a -t vm -s 300m -m n: then you should format the ram disk manually.

eclipse validating xhtml slow-24

If you are not satified with the after the above steps, install jrockit instead of sun jdk, and change some of the vm options by jrocket specification, jrockit is faster than sun jdk.

Some note: On my laptop(Aspire 4745G 4G mem ), windows 7 x64, by default, it takes more than 30 seconds to start eclipse. And after jdk moved to ram disk, it takes 10 seconds to startup.

The validation of my JSF .xhtml files in Eclipse lasts several minutes! It's always the same .xhtml file that requires so much time..

Mainly folks fully concentrate on Java Coding and development (if you are a Java guy :)).

HTML validation error in eclipse as those doesn’t really matters ;).

Step 3) Now let’s take a look at Eclipse Setting to resolve this.Follow these steps to speed up your eclipse as a super fast IDE , it works for 32 & 64 bit version eclipse/jdk on my windows 7 x64. Disable antivirus software, or add your jdk & eclipse & workspace & other related folder to white list in your antivirus software. Disable unecessary validations and startup action in eclipse reference. Modify to set the Xmn(new generation size), Xms and Xmx, enable parallel GC -vm C:/jdk1.6.0_25/bin -startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502–launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502 -product org.product –launcher.default Action open File –launcher.The only error messages on "opened, but not closed" xhtml tags as well as "closed, but not having open tag".Few other error messages that may come from SAX parser. The XHTML Validator was made when there were no validation for XHTML files at all (Not remember exact versions of WST, but nowadays there is some validation from WST HTML validator: not for all the XHTML's, since it is HTML validationl; also WST validation requires DOM-Document to be created, so it works much later than our XHTML Validator and requires more resources (since the document is to be parsed and DOM Tree is actually validated).Hello Friends, It’s been long time I’ve posted on blog but now I’m back with lots of Java Tutorials and Tips. Let me start with “How about stopping validation on .

Comments are closed.