[JBoss JIRA] Created: (JBIDE-8199) Support named packages
by Alexey Kazakov (JIRA)
Support named packages
----------------------
Key: JBIDE-8199
URL: https://issues.jboss.org/browse/JBIDE-8199
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
2.4. Named packages
Seam Solder allows you to annotate the package @Named, which causes every bean defined in
the package to be given its default name. Package annotations are defined in the file package-
info.java. For example, to cause any beans defined in com.acme to be given their default name:
@Named
package com.acme
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8197) Support @Requires annotation
by Alexey Kazakov (JIRA)
Support @Requires annotation
----------------------------
Key: JBIDE-8197
URL: https://issues.jboss.org/browse/JBIDE-8197
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
2.1.2. @Requires
Annotating a class @Requires will cause the type to be ignored if the class dependencies can be satisfied. Any definitions on the type will not be processed:
• the managed bean, decorator, interceptor or session bean defined by the type
• any producer methods or producer fields defined on the type
• any observer methods defined on the type
For example:
@Requires(EntityManager.class)
class EntityManagerProducer {
@Produces EntityManager getEntityManager() {
...
}
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8196) Support @Veto annotation.
by Alexey Kazakov (JIRA)
Support @Veto annotation.
-------------------------
Key: JBIDE-8196
URL: https://issues.jboss.org/browse/JBIDE-8196
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
Seam-solder reference guide:
2.1.1. @Veto.
Annotating a class @Veto will cause the type to be ignored, such that any definitions on the type will not be processed, including:
• the managed bean, decorator, interceptor or session bean defined by the type
• any producer methods or producer fields defined on the type
• any observer methods defined on the type
For example:
@Veto
class Utilities {
...
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8547) Exception in CDIProblemMarkerResolutionGenerator
by Viacheslav Kabanovich (JIRA)
Exception in CDIProblemMarkerResolutionGenerator
------------------------------------------------
Key: JBIDE-8547
URL: https://issues.jboss.org/browse/JBIDE-8547
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Daniel Azarov
Fix For: 3.3.0.M1
I have created method
@Inject
public String getX( @Named String a) { return a; }
which was the last method in a class file.
Then I manually reformatted it to
@Inject
public String getX(
@Named
String a) { return a; } }
with 10 empty lines instead of 1 left here for readability.
Then I deleted each set of spaces by selecting it all and using Delete button.
Finally, I started quickly repeat Undo-Save-Redo-Save with fast keys. Several rounds resulted in the exception.
That kind of intensive 'work' may result in other exceptions as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8325) Injection point should be re-validated automatically if any bean with the same bean type created.
by Alexey Kazakov (JIRA)
Injection point should be re-validated automatically if any bean with the same bean type created.
-------------------------------------------------------------------------------------------------
Key: JBIDE-8325
URL: https://issues.jboss.org/browse/JBIDE-8325
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.CR1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M1
1. Create ITestBean interface.
2. Create public class TestBeanImpl implements ITestBean {...}
3. Add @Inject ITestBean foo; field to any bean but TestBeanImpl.
4. Validate the project. @Inject ITestBean foo; is valid since there is the only bean TestBeanImpl to be injected.
5. Create public class TestBeanImpl2 implements ITestBean {...}. Save the file, build the project (using the incremental builder).
6. @Inject ITestBean foo; is not valid anymore because there are two beans TestBeanImpl and TestBeanImpl2 to be injected. But CDI validator doesn't re-validate @Inject ITestBean foo; We have to change/validate the file with the injection to re-validate it and have a marker on this invalid injection.
Slava, let's add
IInjectionPoint getInjections(String fullyQuilifeidTypeName);
method to IBeanManager interface and its implementation. Then assign the issue to me and I will fix this bug in CDI validator.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months