[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9233) Exception in log while quick editing a file

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610830#comment-12610830 ] 

Viacheslav Kabanovich commented on JBIDE-9233:
----------------------------------------------

I have reproduced the issue in much simpler way that also exectly shows what the problem is.
1. Create injection method with a cdi error. make sure that marker is created.
2.Just delete the entire method. Save.
3. Undo (Ctrl-Z)
4. Save (Ctrl-S) and Redo (Ctrl-Y) - only that quickly just once.
5. Exception.

That shows, that while validation started after save, Java allowed change in editor - redo, and updated by editor change (not by build) Java model does not correspond to its saved version that is used in built after last save CDI model.
What can we do other than check existence and locations of what we validating?

> Exception in log while quick editing a file
> -------------------------------------------
>
>                 Key: JBIDE-9233
>                 URL: https://issues.jboss.org/browse/JBIDE-9233
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>    Affects Versions: 3.3.0.M3
>            Reporter: Lukas Jungmann
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 3.3.0.M3
>
>         Attachments: ide.log
>
>
> I have created method 
> @Inject
> public String getX( @Named String a) { return a; }
> which was the last method in a class file.
> Then I manually reformatted it to 
> @Inject
> public String getX( 
> @Named 
> String a) { return a; }	}
> with 10 empty lines instead of 1 left here for readability.
> Then I deleted each set of spaces by selecting it all and using Delete button.
> Finally, I started quickly repeat Undo-Save-Redo-Save with fast keys. Several rounds resulted in the exception found in ide's log.
> That kind of intensive 'work' may result in other exceptions as well.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira