[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
[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