[JBoss JIRA] Created: (JBIDE-6387) Type of a method parameter is null in case of generic method.
by Alexey Kazakov (JIRA)
Type of a method parameter is null in case of generic method.
-------------------------------------------------------------
Key: JBIDE-6387
URL: https://jira.jboss.org/browse/JBIDE-6387
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:
class FarmBroken <U> {
@Inject
public <T extends Animal> void setAnimal(T animal) {
}
@Inject
public void setMan(U man) {
}
}
setMan(U man) has a parameter U man. And IParameter returns IParametedType which is not null.
But setAnimal(T animal) has a parameter which is type variable declared in the generic method. And IParameter.getType() returns null. It's not ok. It should return IParametedType with a signature==QT; and IType == null.
org.jboss.tools.cdi.core.test.tck.InjectionPointTest.testMethodParameter() 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
[JBoss JIRA] Created: (JBIDE-6380) Specializing bean should inherit the qualifiers and name of specialized bean.
by Alexey Kazakov (JIRA)
Specializing bean should inherit the qualifiers and name of specialized bean.
-----------------------------------------------------------------------------
Key: JBIDE-6380
URL: https://jira.jboss.org/browse/JBIDE-6380
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:
@Mock @Specializes
public class MockAsynchronousService extends AsynchronousService {
...
}
@Default @Asynchronous @Named("asyncService")
public class AsynchronousService implements Service{
...
}
then MockAsynchronousService inherits the qualifiers and name of AsynchronousService.
See 4.3 section of the spec.
All the tests of org.jboss.tools.cdi.core.test.tck.BeanSpecializationTest JUnit 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
[JBoss JIRA] Created: (JBIDE-6447) Injection points should not resolve to non-selected alternatives.
by Alexey Kazakov (JIRA)
Injection points should not resolve to non-selected alternatives.
-----------------------------------------------------------------
Key: JBIDE-6447
URL: https://jira.jboss.org/browse/JBIDE-6447
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.:
5.1.4. Inter-module injection
A bean is available for injection in a certain module if:
...
• the bean is either not an alternative, or the module is a bean archive and the bean is a selected alternative of the bean
archive
org.jboss.tools.cdi.core.test.tck.ResolutionByTypeTest.testPolicyNotAvailableInNonDeploymentArchive() should pass.
IBean.isSelectedAlternative() should be implemented.
--
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
[JBoss JIRA] Created: (JBIDE-6498) cannot create bottom-up ws with JBossWS-metro-3.3.1GA
by Lukas Jungmann (JIRA)
cannot create bottom-up ws with JBossWS-metro-3.3.1GA
-----------------------------------------------------
Key: JBIDE-6498
URL: https://jira.jboss.org/browse/JBIDE-6498
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Environment: Version: Helios Release, Build id: 20100616-2317 + JBT from svn r. 22872
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-have JBossAS6-M3 with ws stack changed to JBossWS-metro-3.3.1GA
-create a bottom-up ws in dynamic web project
=> after finishing a wizard error dialog says:
error: Could not find class file for s.S1 error
Error: Could not generate. (use --show-traces to see full traces)
Error: Wsgen invocation failed. Try the '-verbose' switch for more information
after adding "--show-traces" to the command in Java2WSCommand the error message is less cryptic:
error: Could not find class file for s.S
1 error
Error: Could not generate. (use --show-traces to see full traces)
java.lang.RuntimeException: Wsgen invocation failed. Try the '-verbose' switch for more information
at org.jboss.wsf.stack.metro.tools.MetroProviderImpl.provide(MetroProviderImpl.java:195)
at org.jboss.wsf.stack.metro.tools.MetroProviderImpl.provide(MetroProviderImpl.java:98)
at org.jboss.wsf.spi.tools.cmd.WSProvide.generate(WSProvide.java:191)
at org.jboss.wsf.spi.tools.cmd.WSProvide.main(WSProvide.java:79)
--
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