[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7969) Empty error message from KB validator

[Alexey Kazakov (JIRA)]

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

Alexey Kazakov commented on JBIDE-7969:
---------------------------------------

We check the resource before adding an error marker. The problem is that offset of @Injection which has a problem is out of the document. In that case we get BadLocationException and can't count the line number. We log the exception and use "0" as location for such a marker. The question is why it has a wrong location. May be it's a bug of CDI Tools model. So if you see this error again, please look at Problems View. There should be a CDI warining/error marker with "0" location. It's probably the problematic @Inject. Comment it here and it will help us to reproduce the bug.

> Empty error message from KB validator
> -------------------------------------
>
>                 Key: JBIDE-7969
>                 URL: https://issues.jboss.org/browse/JBIDE-7969
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>            Reporter: Max Andersen
>            Assignee: Alexey Kazakov
>             Fix For: 3.2.0.CR1
>
>
> Not sure what triggered it but got about 10 of these in my error log:
> The error message is empty in the error log view; only the stack trace reveals details.
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.ListLineTracker.getLineNumberOfOffset(ListLineTracker.java:140)
> at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161)
> at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:915)
> at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:398)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:223)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:259)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:175)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:126)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:140)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1213)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:440)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:268)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:116)
> at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

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