[JBoss JIRA] Created: (JBIDE-9791) Add JUnit Tests for CDI Packages Without Coverage
by Denis Golovin (JIRA)
Add JUnit Tests for CDI Packages Without Coverage
-------------------------------------------------
Key: JBIDE-9791
URL: https://issues.jboss.org/browse/JBIDE-9791
Project: Tools (JBoss Tools)
Issue Type: Task
Components: CDI
Affects Versions: 3.3.0.M4
Reporter: Denis Golovin
Assignee: Daniel Azarov
Priority: Critical
Fix For: 3.3.0.M4, 3.3.0.Beta1
Attachments: screenshot113.png
Some CDI packages are not covered by JUnit Tests:
org.jboss.tools.cdi.internal.core.project.facet
org.jboss.tools.cdi.xml.beans.model.handlers
org.jboss.tools.cdi.ui.wizard.facet
org.jboss.tools.cdi.seam.config.ui.preferences
org.jboss.tools.cdi.internal.core.refactoring
org.jboss.tools.cdi.ui.refactoring
org.jboss.tools.cdi.seam.config.ui.marker
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9732) CDI Project should provide a built-in bean with type InjectionPoint
by Alexey Kazakov (JIRA)
CDI Project should provide a built-in bean with type InjectionPoint
-------------------------------------------------------------------
Key: JBIDE-9732
URL: https://issues.jboss.org/browse/JBIDE-9732
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M4
{quote}
*5.5.7. Injection point metadata*
...
The container must provide a bean with scope @Dependent, bean type InjectionPoint and qualifier @Default, allowing
dependent objects, as defined in Section 6.4.1, "Dependent objects", to obtain information about the injection point to
which they belong. The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2,
"Passivation capable dependencies".
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9757) CDI Model in a dependent CDI receives out-of-date Java type from used project.
by Viacheslav Kabanovich (JIRA)
CDI Model in a dependent CDI receives out-of-date Java type from used project.
------------------------------------------------------------------------------
Key: JBIDE-9757
URL: https://issues.jboss.org/browse/JBIDE-9757
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M3
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M4
EXECUTE: Create 2 CDI projects: Test1 depends on Test2.
EXECUTE: Create in Test2 two interfaces test.p1.I and test.p2.I
EXECUTE: Create producer in Test2
{code}
package test;
import javax.enterprise.inject.Produces;
import test.p1.I;
public class MyProducer {
@Produces I getI() {
return null;
}
}
{code}
EXECUTE: Create injection in Test2
{code}
package test;
import javax.inject.Inject;
import test.p2.I;
public class MyBean {
@Inject I i;
}
{code}
EXECUTE: Create or modify any bean in Test1 in order to activate its CDI model.
EXECUTE: Modify package in MyBean: change 'import test.p1.I' to 'import test.p2.I', save, change back, save etc.
ASSERT: Open on always correctly suggest to open producer if 'I' is imported from 'p1' and has no suggestions when 'I' is imported from 'p2'.
FAILURE: Error state of injection does not change. (If CDI in Test1 was activated when injection was correct, error marker will never appear; and if CDI in Test1 was activated when injection was incorrect, error marker will stick to it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9795) Abstract classes should not be included into CDI model as beans
by Viacheslav Kabanovich (JIRA)
Abstract classes should not be included into CDI model as beans
---------------------------------------------------------------
Key: JBIDE-9795
URL: https://issues.jboss.org/browse/JBIDE-9795
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M3
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M4
EXECUTE: Create class
{code}
@Named("mybean")
public abstract class MyBean {
}
{code}
ASSERT: There is no bean MyBean available for injection.
ASSERT: Bean name "mybean" is not available for EL.
One exception is the providing of built-in beans (e.g. specification requires CDI implementation to provide bean with type javax.validation.Validator), but such a bean can be provided by CDI implementations in a non-standard way, so that we should ensure the bean instance in model binding it to an abstract type.
The other temporal exception is to be made for handling injection points in abstract types, it should be covered by separate issue. Now both validation, open-ons, tests access injection points through beans obtained with getBeans(IPath). We should consider migrating to getInjections(IPath), but that may involve extensive changes. So, let method getBeans(IPath) be out of the scope of this issue, and let us comment it properly that it currently returns both beans and bean-like CDI annotated objects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9672) Ctrl+Shift+G on a producer doesn't look for injection points and ELs
by Alexey Kazakov (JIRA)
Ctrl+Shift+G on a producer doesn't look for injection points and ELs
--------------------------------------------------------------------
Key: JBIDE-9672
URL: https://issues.jboss.org/browse/JBIDE-9672
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Priority: Critical
Fix For: 3.3.0.M4
1. Import tck project from o.j.t.cdi.core.test. Add all the sources from o.j.t.cdi.core.test/resources/tck to the project source folder.
2. Add the following class to the project:
{code}
package org.jboss.jsr299.tck.tests.lookup.typesafe.resolution;
import javax.enterprise.inject.Produces;
import javax.inject.Inject;
import javax.inject.Named;
public class Zoo {
@Inject @Wild Cat cat;
@Inject @Wild PetShop p;
String str = "#{aaa.aslan}";
// @Produces @Named("aaa") @Wild PetShop petShop;
@Produces @Named("aaa") @Wild PetShop getPetShop() {
return null;
}
}
{code}
3. Ctrl+Shift+G on getPetShop(). It should find String str = "#{aaa.aslan}"; and @Inject @Wild PetShop p;
4. Comment the producer method. Uncomment the producer field. Ctrl+Shift+G on the field should also find the same EL and injection point.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBDS-1698) Weak Modeshape Performance
by Pavol Srna (JIRA)
Weak Modeshape Performance
--------------------------
Key: JBDS-1698
URL: https://issues.jboss.org/browse/JBDS-1698
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Modeshape
Affects Versions: 5.0.0.M2
Reporter: Pavol Srna
Fix For: 5.0.0.M3
1) Import Parts Model Project Set Example (Help -> Project Examples... -> Teiid Designer -> ..)
2) Right click on PartsProject and select ModeShape -> Publish
The ModeShape publish dialog appears on the screen after more then 2 minutes. On the first look it seems like frozen, but after cca 2 minutes starts everything to work.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months