Bugzilla – Full Text Bug Listing
| Summary: | Provide way to trigger validation | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Florian Philipp <eclipse> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Hi Florian, did you try to use the ValidatingEditorCallback? Ah, thanks. Now that you told me the class name I was able to find some hints on the web on how to use this. Is this documented anywhere? (In reply to comment #2) > Is this documented anywhere? I'm afraid it is not. Closing bug which were set to RESOLVED before Eclipse Neon.0. |
Build Identifier: 20100617-1415 When I start my RCP application or open a file in it, the validation is not triggered automatically. So I see the content, complete with outline and syntax highlighting but parser errors are not shown and my own validators are not executed. I need to make some change to the file, for example inserting a blank line, in order to trigger evaluation. It is my understanding that this is a desired behavior because it avoids possibly resource intensive validations and builds. However, there should be some way to trigger validation nonetheless. I tried the following code snippet: for(IProject project: ResourcesPlugin.getWorkspace().getRoot().getProjects()) for(IResource member: project.members()) if(member.getType() == IResource.FILE) member.touch(new NullProgressMonitor()); It did not work, though. Since the documentation for IResource.touch specifically states that it can be used for triggering rebuilds and that it causes a resource change event, I'm wondering whether XText's behavior is really conforming. Reproducible: Always Steps to Reproduce: 1. Extend AbstractDeclarativeValidator 2. Open a new file which contains an error 3. Notice that no error is shown 4. Make a minor change to the file 5. Notice that the error suddenly appears 6. Restart the application 7. Notice that the error is once again gone