Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351922 - An internal error occurred during: "Validation"
Summary: An internal error occurred during: "Validation"
Status: NEW
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.validation (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: wst.validation CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 04:04 EDT by Philippe Marschall CLA
Modified: 2011-08-07 08:00 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Marschall CLA 2011-07-13 04:04:18 EDT 
What steps will reproduce the problem?
1. This happened when importing a project from SVN using m2e


-- Error Details --
Date: Wed Jul 13 09:48:15 CEST 2011
Message: An internal error occurred during: "Validation".
Severity: Error
Product: Eclipse SDK 3.7.0.v201106131736 (org.eclipse.sdk.ide)
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=I20110613-1736
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -data C:\local\workspaces\test-workspace

Exception Stack Trace:
java.lang.IllegalStateException: IWAE0019E There was a problem deserializing a string. A boolean was expected but not found. 
	at org.eclipse.wst.validation.internal.Deserializer.getBoolean(Deserializer.java:33)
	at org.eclipse.wst.validation.internal.model.FilterRule.create(FilterRule.java:78)
	at org.eclipse.wst.validation.internal.model.FilterGroup.create(FilterGroup.java:63)
	at org.eclipse.wst.validation.internal.ValPrefManagerGlobal.loadValidator(ValPrefManagerGlobal.java:173)
	at org.eclipse.wst.validation.internal.ValPrefManagerGlobal.loadValidators(ValPrefManagerGlobal.java:128)
	at org.eclipse.wst.validation.internal.ValPrefManagerGlobal.getValidators(ValPrefManagerGlobal.java:111)
	at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:347)
	at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221)
	at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220)
	at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1287)
	at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197)
	at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745)
	at org.eclipse.wst.validation.internal.ValBuilderJob.finishingValidation(ValBuilderJob.java:161)
	at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:131)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Michael Pellaton CLA 2011-08-07 08:00:29 EDT 
This problem was caused by a corrupted configuration file that lead to parsing problems of the validation preferences.

This bug can be IMHO cancelled.