September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9553) Forge Runtime is lost when eclipse is restarted

by George Gastaldi (JIRA)

Forge Runtime is lost when eclipse is restarted ----------------------------------------------- Key: JBIDE-9553 URL: https://issues.jboss.org/browse/JBIDE-9553 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: George Gastaldi If you configure a new Forge runtime and restart eclipse, the installed Forge runtime disappears from the "Forge Runtime" tab. Tested with the nightly build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9271) Workspace locks/slow when Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project'

by Lincoln Baxter III (JIRA)

Workspace locks/slow when Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project' ------------------------------------------------------------------------------------------------- Key: JBIDE-9271 URL: https://issues.jboss.org/browse/JBIDE-9271 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), maven Environment: Linux Ubuntu x64 Natty Eclipse Indigo 3.7 Java 1.6.0_24 Reporter: Lincoln Baxter III Assignee: Alexey Kazakov Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project' causes the workspace to lock whenever a file is changed. Check out this project: https://github.com/ocpsoft/rewrite Import in to workspace as maven project. Open a source file in API. Change the file. Try to change or save any other file (the workspace locks while it waits for CDI builder to finish.) Very annoying :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

8
28
0 / 0

[JBoss JIRA] Created: (JBIDE-9111) Deadlock when creating a new JSF project

by Fred Bricon (JIRA)

Deadlock when creating a new JSF project ---------------------------------------- Key: JBIDE-9111 URL: https://issues.jboss.org/browse/JBIDE-9111 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M1 Environment: Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_24/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.38.6-27.fc15.x86_64", arch: "amd64", family: "unix" Eclipse Indigo Java EE RC3 20110602-0820 JBoss tools plugins installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ Reporter: Fred Bricon Assignee: Alexey Kazakov Priority: Critical After installing the JBT plugins from the nightly update site on a Eclipse JavaEE Indigo RC3, I created a new JSF project. The creation hanged indefinitely after clicking on finish. See attached threaddump Seems like an upstream issue to me. I couldn't not reproduce it after killing eclipse and restarting. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9571) ELRefactorContributionFactory.createContributionItems(IServiceLocator, IContributionRoot) is very slow on big files

by Denis Golovin (JIRA)

ELRefactorContributionFactory.createContributionItems(IServiceLocator,IContributionRoot) is very slow on big files ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-9571 URL: https://issues.jboss.org/browse/JBIDE-9571 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M3 Reporter: Denis Golovin Assignee: Daniel Azarov Fix For: 3.3.0.Beta1 # EXEC: Import test project from jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsfTest. # EXEC: Open WebContent/pages/JBIDE/1479/employee.xhtml and request popup menu for any open tag. # ASSERT :Menu appears right away Now it takes a little while until popup menu appears. Until that eclipse is not responding. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9761) JSF Tools should provide code completion for @ManagedBean(name="")

by Alexey Kazakov (JIRA)

JSF Tools should provide code completion for @ManagedBean(name="") ------------------------------------------------------------------ Key: JBIDE-9761 URL: https://issues.jboss.org/browse/JBIDE-9761 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 3.3.0.M4 The following beans has the same name "user": {code} @MamanedBean public class User {} {code} {code} @MamanedBean(name="user") public class AnotherUser {} {code} {code} @MamanedBean(name="") public class User {} {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9753) multiple content web roots seem to confuse VPE

by Max Rydahl Andersen (JIRA)

multiple content web roots seem to confuse VPE ---------------------------------------------- Key: JBIDE-9753 URL: https://issues.jboss.org/browse/JBIDE-9753 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.3.0.M3 Reporter: Max Rydahl Andersen Assignee: Yahor Radtsevich Priority: Blocker Fix For: 3.3.0.M4 import AS 7 quickstarts kitchensink and even though the template files are in the right place it doesn't pick it up. See http://screencast.com/t/7FI8I2hZBP -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
24
0 / 0

[JBoss JIRA] Created: (JBIDE-9683) CDI validation problems which may cause non-portable behavior results should be WARNINGs by default.

by Alexey Kazakov (JIRA)

CDI validation problems which may cause non-portable behavior results should be WARNINGs by default. ---------------------------------------------------------------------------------------------------- Key: JBIDE-9683 URL: https://issues.jboss.org/browse/JBIDE-9683 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M4 For example if you create a @Typed stereotype then CDI validator mark it as ERROR by default. It should be changed to WARNING. Another example a stereotype with qualifier annotation other than @Named. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9684) CDI validator fails if a producer has a qualifier declared by inner interface

by Alexey Kazakov (JIRA)

CDI validator fails if a producer has a qualifier declared by inner interface ----------------------------------------------------------------------------- Key: JBIDE-9684 URL: https://issues.jboss.org/browse/JBIDE-9684 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 1. Create the following code: {code} public class A { @Qualifier @Retention(RUNTIME) public @interface T {} } {code} {code} public class B extends C { @Produces @T Object t; } {code} 2. Save the files. 3. See Eclipse log: {code} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:532) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:442) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:318) at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:116) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) ... 2 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9699) Injection points of disposer methods are not validated

by Alexey Kazakov (JIRA)

Injection points of disposer methods are not validated ------------------------------------------------------ Key: JBIDE-9699 URL: https://issues.jboss.org/browse/JBIDE-9699 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 See JSR-299: {quote} *3.3.6. Declaring a disposer method* ... In addition to the disposed parameter, a disposer method may declare additional parameters, which may also specify qualifiers. These additional parameters are injection points. {quote} So we should treat all the parameters of disposer methods (except disposer parameters) as injection points. For instance the following *@TestQualifier1 String s1* injected parameter should be marked as unsatisfied dependency: {code} public void foo2(@Disposes @TestQualifier3 String s, @TestQualifier1 String s1) { } @Produces @TestQualifier3 public String foo3() { return ""; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9722) Injection point annotated with @New should be resolved even if bean class does not belong to a bean archive.

by Viacheslav Kabanovich (JIRA)

Injection point annotated with @New should be resolved even if bean class does not belong to a bean archive. ------------------------------------------------------------------------------------------------------------ Key: JBIDE-9722 URL: https://issues.jboss.org/browse/JBIDE-9722 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 See JSR-299 3.12. @New qualified beans. For each managed bean, and for each session bean, a second bean exists which: • has the same bean class, • has the same bean types, • has the same bean constructor, initializer methods and injected fields, and • has the same interceptor bindings. However, this second bean: • has scope @Dependent, • has a exactly one qualifier: @javax.enterprise.inject.New(X.class) where X is the bean class, • has no bean EL name, • has no stereotypes, • has no observer methods, producer methods or fields or disposer methods, and • is not an alternative, and • is enabled, in the sense of Section 5.1.2, "Enabled and disabled beans", if and only if some other enabled bean has an injection point with the qualifier @New(X.class) where X is the bean class. This bean is called the @New qualified bean for the class X. Note that this second bean exists—and may be enabled and available for injection—even if the first bean is disabled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
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 September 2011