[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, 10 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, 10 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, 10 months
[JBoss JIRA] (JBIDE-9906) CDI model should load exported jars from parent projects
by Alexey Kazakov (Created) (JIRA)
CDI model should load exported jars from parent projects
--------------------------------------------------------
Key: JBIDE-9906
URL: https://issues.jboss.org/browse/JBIDE-9906
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M4
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M4
EXECUTE: Create two CDI projects: Project1 and Project2. Project2 should depends on Project1 (Project1 should be included in the class path of Project2).
EXECUTE: Add Seam International extension module to the Project1 (seam-international.jar). Set it as exported jar in Preferences->Java Build Path->Order and Export
EXECUTE: In each project, create a Java class declaring a String field assigned to a string "#{bundles.}". Invoke content assist after the dot.
ASSERT: A lot of suggestions appear including 'bundles.com.sun.corba.se.impl.logging.LogStrings' - they come from 'resources.jar' in JRE.
FAILURE: bundles.com... appears only in Project1 but doesn't appear in Project2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] (JBIDE-10007) ensure that BPEL and Savara can be easily installed from JBoss Tools M4
by Nick Boldt (Created) (JIRA)
ensure that BPEL and Savara can be easily installed from JBoss Tools M4
-----------------------------------------------------------------------
Key: JBIDE-10007
URL: https://issues.jboss.org/browse/JBIDE-10007
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: BPEL, bpm, Build/Releng, Savara, updatesite, UpStream
Affects Versions: 3.3.0.M4
Reporter: Nick Boldt
Assignee: Robert (Bob) Brodt
Fix For: 3.3.0.M4
May need to add more requirements (graphiti, gmf, gef, bpmn2) to http://download.jboss.org/jbosstools/updates/requirements/, or
simply link to more upstream URLs in
https://svn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/aggrega...
(and maybe add more <repository> entries to https://svn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml ?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months