[JBoss JIRA] Created: (JBIDE-6255) NullPointerException in CDI Validator
by Victor Rubezhny (JIRA)
NullPointerException in CDI Validator
-------------------------------------
Key: JBIDE-6255
URL: https://jira.jboss.org/jira/browse/JBIDE-6255
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.1.0.GA
Reporter: Victor Rubezhny
Assignee: Alexey Kazakov
Fix For: 3.2.next
Sometimes at startup an exception rised:
java.lang.NullPointerException
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:212)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:99)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:78)
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.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
[JBoss JIRA] Created: (JBIDE-6474) Injection points with a parameterized type should resolve to corresponding beans according to CDI spec.
by Alexey Kazakov (JIRA)
Injection points with a parameterized type should resolve to corresponding beans according to CDI spec.
-------------------------------------------------------------------------------------------------------
Key: JBIDE-6474
URL: https://jira.jboss.org/browse/JBIDE-6474
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.M1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.M2
See the spec.:
5.2.3. Assignability of raw and parameterized types.
A parameterized bean type is considered assignable to a parameterized required type if they have identical raw type and for each parameter:
• the required type parameter and the bean type parameter are actual types with identical raw type, and, if the type is parameterized, the bean type parameter is assignable to the required type parameter according to these rules, or
• the required type parameter is a wildcard, the bean type parameter is an actual type and the actual type is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or
• the required type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable to or assignable from the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or
• the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable to the upper bound, if any, of the type variable, or
• the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound, if any, of the bean type parameter.
All the tests in org.jboss.tools.cdi.core.test.tck.AssignabilityOfRawAndParameterizedTypesTest should pass.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
[JBoss JIRA] Created: (JBIDE-6445) OpenOn for Injection points hands Eclipse for a while.
by Alexey Kazakov (JIRA)
OpenOn for Injection points hands Eclipse for a while.
------------------------------------------------------
Key: JBIDE-6445
URL: https://jira.jboss.org/browse/JBIDE-6445
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.next
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Priority: Critical
Fix For: 3.2.next
1. Create a big CDI project (you can take our tests project from *.cdi.core.test plug-in).
2. Open any java fle with @Inject
3. Try to Ctrl+Click on @Inject. Works fine.
4. Restart Eclipse.
5. Ctrl+Click on the same @Inject. Eclipse hangs for a while (on my PC with the project from *.cdi.core.test, it takes about a minute) until builders complete working. And only after that you will see OpenOn dialog.
Maybe it's better to show the dialog always and do a real search only if user click on our hyperlink? Or is it possible to show progress dialog while the project is being built? How Java OpenOns work?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months