March 2011 - jbosstools-issues - Jboss List Archives

[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

3
3
0 / 0

[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

3
3
0 / 0

[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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7635) Quick fix for "No bean is (Multiple beans are) eligible for injection to the injection point" error markers

by Daniel Azarov (JIRA)

Quick fix for "No bean is (Multiple beans are) eligible for injection to the injection point" error markers ----------------------------------------------------------------------------------------------------------- Key: JBIDE-7635 URL: https://jira.jboss.org/browse/JBIDE-7635 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer to delete @Inject annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8550) QuickFix for "Managed bean xxx which declares a passivating scope yyy must be passivation capable [JSR-299 §6.6.4]"

by Alexey Kazakov (JIRA)

QuickFix for "Managed bean xxx which declares a passivating scope yyy must be passivation capable [JSR-299 §6.6.4]" ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8550 URL: https://issues.jboss.org/browse/JBIDE-8550 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M1 We should add java.io.Serializable to the list of implemented interfaces for the bean in this case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
5
0 / 0

[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

3
3
0 / 0

[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

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8265) Let

by Denis Golovin (JIRA)

Let --- Key: JBIDE-8265 URL: https://issues.jboss.org/browse/JBIDE-8265 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Denis Golovin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6768) Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2.

by Alexey Kazakov (JIRA)

Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2. ----------------------------------------------------------------------------- Key: JBIDE-6768 URL: https://jira.jboss.org/browse/JBIDE-6768 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x Now we use V1. V2 has some improvements. For instance we can use Validation->Settings page for include/exclude rules. This framework is being developed yet but seems to be stable enough. -- 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

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6619) VPE Resizer is not shown on XULRunner 1.9.2

by Yahor Radtsevich (JIRA)

VPE Resizer is not shown on XULRunner 1.9.2 ------------------------------------------- Key: JBIDE-6619 URL: https://jira.jboss.org/browse/JBIDE-6619 Project: Tools (JBoss Tools) Issue Type: Bug Components: aop Affects Versions: 3.2.0.M2 Environment: XULRunner 1.9.2 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M2 Compare screenshots on both versions of XULRunner: 1.9.1 and 1.9.2 (screenshots.png). -- 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

14 years, 8 months

3
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2011