September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5991) no error message when no web.xml in a dynamic web project

by Feng Qian (JIRA)

no error message when no web.xml in a dynamic web project --------------------------------------------------------- Key: JBIDE-5991 URL: https://jira.jboss.org/jira/browse/JBIDE-5991 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.0.CR2 Reporter: Feng Qian We always use a dynamic web project to generate web service. When generate web service, we need to update the web.xml. But a dynamic web project may not have no web.xml. In this case, we should generate a default web.xml for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5990) noisy in logs when generate web service using a wsdl

by Feng Qian (JIRA)

noisy in logs when generate web service using a wsdl ---------------------------------------------------- Key: JBIDE-5990 URL: https://jira.jboss.org/jira/browse/JBIDE-5990 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.0.CR2 Reporter: Feng Qian When use the web service wizard to generate web service by a wsdl, there are some warning logs in the error view. Such as 'Parsing wsdl....'. We should remove them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5972) A bean doesn't have built-in qualifier types.

by Alexey Kazakov (JIRA)

A bean doesn't have built-in qualifier types. --------------------------------------------- Key: JBIDE-5972 URL: https://jira.jboss.org/jira/browse/JBIDE-5972 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See org.jboss.tools.cdi.core.test.tck.DefinitionTest.testQualifiersNonEmpty() JUnit test. It must pass. See CDI spec for details: 2.3.1. Built-in qualifier types Three standard qualifier types are defined in the package javax.enterprise.inject. In addition, the built-in qualifier type @Named is defined by the package javax.inject. Every bean has the built-in qualifier @Any, even if it does not explicitly declare this qualifier, except for the special @New qualified beans defined in Section 3.12, "@New qualified beans". If a bean does not explicitly declare a qualifier other than @Named, the bean has exactly one additional qualifier, of type @Default. This is called the default qualifier. The following declarations are equivalent: @Default public class Order { ... } public class Order { ... } Both declarations result in a bean with two qualifiers: @Any and @Default. The following declaration results in a bean with three qualifiers: @Any, @Default and @Named("ord"). @Named("ord") public class Order { ... } The default qualifier is also assumed for any injection point that does not explicitly declare a qualifier, as defined in Section 3.10, "The default qualifier at injection points". The following declarations, in which the use of the @Inject annotation identifies the constructor parameter as an injection point, are equivalent: public class Order { @Inject public Order(@Default OrderProcessor processor) { ... } } public class Order { @Inject public Order(OrderProcessor processor) { ... } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5973) Bean type declaration has wrong location within text file.

by Alexey Kazakov (JIRA)

Bean type declaration has wrong location within text file. ---------------------------------------------------------- Key: JBIDE-5973 URL: https://jira.jboss.org/jira/browse/JBIDE-5973 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See org.jboss.tools.cdi.core.test.tck.DefinitionTest.testBeanTypesNonEmpty() JUnit test. It must pass. Example: @FishStereotype @RequestScoped class RedSnapper implements Animal { } RedSnapper and Animal have start position equaled -1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5934) Web service client wizard bad behaviour

by Libor Zoubek (JIRA)

Web service client wizard bad behaviour --------------------------------------- Key: JBIDE-5934 URL: https://jira.jboss.org/jira/browse/JBIDE-5934 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Libor Zoubek 1. On the 2nd page of WSClient wizard (type of JBossWS) is allowed to enter invalid package name. We should perform validation. One can then get invalid generated sources (which wizard says) or NullPointerException (when package name contains @ ) 2. Wizard should warn user when it is possible to overwrite some source files. Consider case when user creates web service (for example uses our 'Sample web service wizard'). He decides to generate client. Opens New web Service Client Wizard, enters service's WSDL and clicks Finish. Because of the fact, that package name is by default derived from namespaces found in WSDL, generated proxies overwrite service implementation without warning. Wizard should just check, if filled 'Package Name' exists or not and warn about possible risks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5928) OpenOn for injection point goes to corresponding class even if it injects a producer.

by Alexey Kazakov (JIRA)

OpenOn for injection point goes to corresponding class even if it injects a producer. ------------------------------------------------------------------------------------- Key: JBIDE-5928 URL: https://jira.jboss.org/jira/browse/JBIDE-5928 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.next In that case it should set cursor to the producer field or method but not to a parent class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6258) CDI model set wrong position for parameted types.

by Alexey Kazakov (JIRA)

CDI model set wrong position for parameted types. ------------------------------------------------- Key: JBIDE-6258 URL: https://jira.jboss.org/jira/browse/JBIDE-6258 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next For example: public class SpiderProducerWildCardType_Broken<T> { @Produces public FunnelWeaver<? extends T> getAnotherFunnelWeaver; } This producer has FunnelWeaver<? extends T> type but position for it is wrong and points to "T>". org.jboss.tools.cdi.core.test.tck.ValidationTest.testParameterizedReturnTypeWithWildcard() should pass. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6252) CDI bean manager doesn't resolve disposer methods.

by Alexey Kazakov (JIRA)

CDI bean manager doesn't resolve disposer methods. -------------------------------------------------- Key: JBIDE-6252 URL: https://jira.jboss.org/jira/browse/JBIDE-6252 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Implement CDIProject.resolveDisposers(IProducerMethod) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6263) There is no any Type Declarations in CDI model for type variables.

by Alexey Kazakov (JIRA)

There is no any Type Declarations in CDI model for type variables. ------------------------------------------------------------------ Key: JBIDE-6263 URL: https://jira.jboss.org/jira/browse/JBIDE-6263 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next For example: public class SpiderProducerVariableType_Broken<T> { @Produces T getAnotherFunnelWeaver2; @Produces public T create(InjectionPoint point) { return null; } @Produces public <T> T create2(InjectionPoint point) { return null; } } There should be T type declaratios for these producers. org.jboss.tools.cdi.core.test.tck.ValidationTest.testParameterizedType() should pass. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6339) All initializer method parameters should be recognized as injection points.

by Alexey Kazakov (JIRA)

All initializer method parameters should be recognized as injection points. --------------------------------------------------------------------------- Key: JBIDE-6339 URL: https://jira.jboss.org/browse/JBIDE-6339 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See the spec. Section 3.9.1 - Declaring an initializer method. - All initializer method parameters are injection points. Section 3.7.1 - Declaring a bean constructor. - All parameters of a bean constructor are injection points. All the tests of org.jboss.tools.cdi.core.test.tck.InjectionPointTest should pass. -- 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

15 years, 6 months

4
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 2010