[
https://issues.jboss.org/browse/JBIDE-8709?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich edited comment on JBIDE-8709 at 5/27/11 2:38 PM:
-----------------------------------------------------------------------
In my case, Validation builder is registered before CDI builder, which Alexey already
found as possible cause for some other failures. So, when stereotype/qualifier type is
removed, on started build, first validation runs with invalid CDI model.
That also might explain unrelated el error messages, though I was not able to reproduce
that. Alexey should we try resolve this issue by providing correct order for builders,
without making CDI model more error-proof by additional checks?
was (Author: scabanovich):
In my case, Validation builder is registered before CDI builder, which Alexey already
found as possible cause for some other failures. So, when stereotype/qualifier type is
removed, on started build, first validation runs with invalid CDI model.
Removing class which there are still references too causes error
logging/unrelated invalidation errors
------------------------------------------------------------------------------------------------------
Key: JBIDE-8709
URL:
https://issues.jboss.org/browse/JBIDE-8709
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: Max Rydahl Andersen
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M2
I created a qualifier annotation called Asynchronous and reference it in an inject:
@Inject @Asynchronous Foo bar;
then I deleted the Asynchrounous class and the above error becomes a compile error ( that
is expected )
but all CDI validation now reported nothing was correct (alot of EL validation errors not
related to bar reference) and
the following was logged in errors:
Java Model Exception: Java Model Status [Asynhronous.java [in
org.jboss.weld.examples.pastecode.session [in src/main/java [in weld-jsf-pastecode]]] does
not exist]
at
org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at
org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.SourceType.getAnnotations(SourceType.java:191)
at
org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.init(AbstractMemberDefinition.java:66)
at
org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.init(AbstractTypeDefinition.java:60)
at
org.jboss.tools.cdi.internal.core.impl.definition.AnnotationDefinition.init(AnnotationDefinition.java:60)
at
org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:50)
at
org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:54)
at
org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.createAnnotation(DefinitionContext.java:232)
at
org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.getAnnotationKind(DefinitionContext.java:226)
at
org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getQualifierDeclarations(AbstractBeanElement.java:172)
at
org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getQualifierDeclarations(AbstractBeanElement.java:165)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:307)
at
org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1349)
at
org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:465)
at
org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:366)
at
org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:270)
at
org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validate(ValidatorManager.java:113)
at
org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:84)
at
org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Missing classes should not *stop* our validator since that is a common scenario so not
sure what is going on ? Some stale model references maybe?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira