Bug 210875 - Weird validation errors persisted after saving with auto-build (auto validation)
Summary: Weird validation errors persisted after saving with auto-build (auto validation)
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: OHF (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ohf.h3et-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-25 17:48 EST by Dennis Nguyen CLA
Modified: 2012-01-05 13:31 EST (History)
0 users

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 Dennis Nguyen CLA 2007-11-25 17:48:46 EST 
Steps To Reproduce:
When fixing validation issues and saving, sometimes weird validations show up.  Repeated saving does not make them go away, however a forceable validate does.  Saving should always cause a forceable validate to occur.


More information:
This behavior is confirmed, but unable to reproduce reliably. Trying to twist the validator action from instanceeditor.ui.validation and example.ui.validation; then wait to see if it fix the problem. 

Preliminary analysis believe this may be caused by:
1. Source validator don't remove old errors (fixed but can't confirm if this is the cause)
2. Validator terminate too early (try to avoid unnecessary checking)
3. Validator builder was not called properly (either a problem with WST or Eclipse itself)
Comment 1 Dennis Nguyen CLA 2007-11-28 02:01:58 EST 
Similar symptom may also occur when project does not yet configure WST validation builder as one of its builder. To avoid this confusion, new HL7 project will be created with WST validation builder setup as default builder.