[JBoss JIRA] Created: (JBIDE-8018) Problem marker for injection which resolves to a proxible bean.
by Alexey Kazakov (JIRA)
Problem marker for injection which resolves to a proxible bean.
---------------------------------------------------------------
Key: JBIDE-8018
URL: https://issues.jboss.org/browse/JBIDE-8018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.CR1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
5.4.1. Unproxyable bean types
- Classes which don't have a non-private constructor with no parameters cannot be proxied by the container.
- If an injection point whose declared type cannot be proxied by the container resolves to a bean with a normal scope, the container automatically detects the problem and treats it as a deployment problem.
For instance:
@ApplicationScoped
public class MavenContainer
{
}
...
then the following injection should not have the problem marker:
@Inject
public MavenCoreFacetImpl(MavenContainer container)
{
this.container = container;
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7947) 3.1 error is on class but should be on the field
by Max Andersen (JIRA)
3.1 error is on class but should be on the field
------------------------------------------------
Key: JBIDE-7947
URL: https://issues.jboss.org/browse/JBIDE-7947
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Max Andersen
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
@Singleton
public class Test {
public String xxx;
public String xyz;
}
Gives something like this on the class for every public field:
Description Resource Path Location Type
Managed bean with a public field must be @Dependent scoped [JSR-299 §3.1] MockOptionTestPlugin.java /forge-shell/src/test/java/org/jboss/seam/forge/shell/test/command line 36 CDI Problem
That error should be on the field, not the class.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7909) New Interceptor Binding Type Wizard should validate interceptor bindings which are going to be inherited.
by Alexey Kazakov (JIRA)
New Interceptor Binding Type Wizard should validate interceptor bindings which are going to be inherited.
---------------------------------------------------------------------------------------------------------
Key: JBIDE-7909
URL: https://issues.jboss.org/browse/JBIDE-7909
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.CR1
9.1.1. Interceptor binding types with additional interceptor bindings
...
Interceptor binding types declared @Target(TYPE) may not be applied to interceptor binding types declared
@Target({TYPE, METHOD}).
1. Create an interceptor binding type with @Target(TYPE): TypedBinding
2. Open New Interceptor Binding Type wizard.
3. Select @Target(TYPE, METHOD)
4. Add TypedBinding to Interceptor Bindings field.
5. There should be a warning that TypedBinding may not be applied to the interceptor binding declared @Target({TYPE, METHOD}) since it declared @Target(TYPE).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7998) CDI Model doesn't store project dependencies.
by Alexey Kazakov (JIRA)
CDI Model doesn't store project dependencies.
---------------------------------------------
Key: JBIDE-7998
URL: https://issues.jboss.org/browse/JBIDE-7998
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.CR1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.2.0.CR1
Suppose we have CDI projects A, B, C. C depends on B, B depends on A. If we build all the projects then CDI model of B has two links to A and C. That's right. But when you restart eclipse, then B would lose the link to C. Please fix it and give a name of the unit test to help QA team to verify the fix.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7950) Abstract classes is being considered injectable
by Max Andersen (JIRA)
Abstract classes is being considered injectable
-----------------------------------------------
Key: JBIDE-7950
URL: https://issues.jboss.org/browse/JBIDE-7950
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Max Andersen
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 3.2.0.CR1
public interface Project {
}
public abstract class AbstractProject implements Project {
}
public class ProjectImpl extends AbstractProject {
}
@Singleton
public class CurrentProject {
@Produces
@Default
@Dependent
public Project getCurrent()
}
and then:
@Inject Project project;
And I get "Multiple beans are eligible for injection to the injection point"
Open All elgible beans seem to consider getCurrent() *and* the abstract class - but for some reason not ProjectImpl as elgible.
Should it not just be getCurrent() ?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months