June 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-627) Clarify the implementation and usage of WeldClass.getWeldMethods, WelldClass.getDeclaredWeldMethods

by Marius Bogoevici (JIRA)

Clarify the implementation and usage of WeldClass.getWeldMethods, WelldClass.getDeclaredWeldMethods --------------------------------------------------------------------------------------------------- Key: WELD-627 URL: https://jira.jboss.org/browse/WELD-627 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Fix For: 1.1.0.BETA2 The goal for getWeldMethods and getDeclaredWeldMethods is to mimic the behavior of getMethods and getDeclaredMethods as they are defined on java.lang.Class. Introduce a new method - called e.g. getWeldBusinessMethods that returns the methods of the class that can be used for business methods invocations on a particular bean. -- 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

12 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (WELD-516) RunnableDecorator incorrectly assumes >0 Runnable beans

by Morten Christensen (JIRA)

RunnableDecorator incorrectly assumes >0 Runnable beans ------------------------------------------------------- Key: WELD-516 URL: https://jira.jboss.org/jira/browse/WELD-516 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Java 6 + WeldSE Reporter: Morten Christensen The class org.jboss.weld.environment.se.threading.RunnableDecorator incorrectly assumes that there will be at least one bean that implements Runnable. If there are no beans that implements Runnable then an error like this will happen: org.jboss.weld.DeploymentException: Injection point has unstatisfied dependencies. Injection point: field org.jboss.weld.environment.se.threading.RunnableDecorator.runnable; Qualifiers: [@javax.enterprise.inject.Default()] at org.jboss.weld.Validator.validateInjectionPoint(Validator.java:232) at org.jboss.weld.Validator.validateBean(Validator.java:80) at org.jboss.weld.Validator.validateRIBean(Validator.java:100) at org.jboss.weld.Validator.validateBeans(Validator.java:282) at org.jboss.weld.Validator.validateDeployment(Validator.java:267) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:389) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:81) at org.jboss.weld.environment.se.StartMain.go(StartMain.java:45) at org.jboss.weld.environment.se.StartMain.main(StartMain.java:57) I guess the field "runnable" inside this class should be changed to use Instance<Runnable> instead. -- 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

12 years, 9 months

6
12
0 / 0

[JBoss JIRA] Created: (CDI-34) Make special note in the spec about @Named beans (via a stereotype) cannot be selected with Instance.select()

by Shane Bryzak (JIRA)

Make special note in the spec about @Named beans (via a stereotype) cannot be selected with Instance.select() ------------------------------------------------------------------------------------------------------------- Key: CDI-34 URL: https://issues.jboss.org/browse/CDI-34 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Shane Bryzak Priority: Minor For example, say we have the following bean: public @Model class Foo implements IFoo { } And we have the following injection point within another bean: @Inject Instance<Foo> fooInstance; It is not possible to select Foo via name using the Instance: // This results in an UnsatisfiedDependencyException Foo foo = fooInstance.select(new NamedLiteral("foo")).get(); Instead, Foo must be annotated directly with the @Named annotation itself: /* * This Foo can be selected by name */ public @Named @RequestScoped Foo implements IFoo { } This special case might be worthwhile mentioning in the next revision of the spec. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (CDITCK-212) DestroyedInstanceReturnedByGetTest assumes that the application scope can be destroyed and then re-created

by Stuart Douglas (JIRA)

DestroyedInstanceReturnedByGetTest assumes that the application scope can be destroyed and then re-created ---------------------------------------------------------------------------------------------------------- Key: CDITCK-212 URL: https://issues.jboss.org/browse/CDITCK-212 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Stuart Douglas Context applicationContext = getCurrentManager().getContext(ApplicationScoped.class); destroyContext(applicationContext); setContextActive(applicationContext); myApplicationBeanInstance = applicationContext.get(myApplicationBean); The spec does not require that the application scope can be destroyed and re-created, if fact it could be argued that this behaviour violates the spec, as the application context is supposed to last for the lifetime of the application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (CDITCK-213) Interceptor classes in TCK do not follow the Interceptor spec

by Bob Nettleton (JIRA)

Interceptor classes in TCK do not follow the Interceptor spec ------------------------------------------------------------- Key: CDITCK-213 URL: https://issues.jboss.org/browse/CDITCK-213 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Bob Nettleton There are some interceptor-related suites in the CDI TCK that are not portable in some situations. The interceptor classes listed here: org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.interceptorOrder.MissileInterceptor org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.MissileInterceptor org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.simpleInterception.MissileInterceptor These interceptor classes do not have a public, no-args constructor, which is required by the Interceptor 1.1 specification. This means that the tests may not be portable to all environments, since application servers may choose to treat this as an error condition. The following tests are affected by this issue: org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.interceptorOrder.SessionBeanInterceptorOrderTest.testInterceptorsDeclaredUsingInterceptorsCalledBeforeInterceptorBinding org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest.testNonContextualSessionBeanReferenceIsIntercepted org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.simpleInterception.SessionBeanInterceptorDefinitionTest.testSessionBeanIsIntercepted I request that these tests be excluded from the 1.0.4 suite, and that the interceptors be fixed for subsequent versions of the test suite. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (CDITCK-219) SessionContextTest.testSessionContextDestroyedWhenHttpSessionTimesOut uses too short of a sleep delay time

by Bob Nettleton (JIRA)

SessionContextTest.testSessionContextDestroyedWhenHttpSessionTimesOut uses too short of a sleep delay time ---------------------------------------------------------------------------------------------------------- Key: CDITCK-219 URL: https://issues.jboss.org/browse/CDITCK-219 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Bob Nettleton The following test case: org.jboss.jsr299.tck.tests.context.session.SessionContextTest.testSessionContextDestroyedWhenHttpSessionTimesOut uses the following line to sleep after asking the application server to invalidate the session: " Thread.sleep(1500);" The test attempts to verify that the session context is destroyed properly after the timeout. The problem with this test is that it appears as if it could potentially introduce a timing problem. Since Thread.sleep() behaves slightly differently for each platform, and as far as I can tell is not even guaranteed to sleep as long as requested in some situations, there is a chance that the client may make the second request before 1.5 seconds has expired. Since the behavior of System.getTimeMillis() is also system-dependent, I'd be inclined to think that 1.5 seconds is probably not a long enough timeout in order to keep this test from having intermittent failures. I request that this test case be excluded, and that this test be modified in a later version of the TCK to use a larger sleep value. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-217) InjectionIntoWebServiceEndpoint test uses hard-coded HTTP port

by Bob Nettleton (JIRA)

InjectionIntoWebServiceEndpoint test uses hard-coded HTTP port -------------------------------------------------------------- Key: CDITCK-217 URL: https://issues.jboss.org/browse/CDITCK-217 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Bob Nettleton The following test in the CDI TCK: org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.testInjectionIntoWebServiceEndpoint appears to use a hard-coded HTTP port in the following web service client class: org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.SheepWSEndPointService This test is quite different from the rest of the suite, in that the configured HTTP port is not used in this client. It appears that the test is non-portable in its current state. I request that this test be excluded. Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (WELD-811) Hierarchy injection is not working with external annotation type.

by Rogerio Baldini (JIRA)

Hierarchy injection is not working with external annotation type. ----------------------------------------------------------------- Key: WELD-811 URL: https://issues.jboss.org/browse/WELD-811 Project: Weld Issue Type: Bug Components: Weld SPI Affects Versions: 1.1.0.CR3 Reporter: Rogerio Baldini In WeldClassImpl constructor, superclass is set as an Object.class when annotatedType is instanceof ExternalAnnotatedType (discovered flag). Why? This behavior causes a non injection of superclasses fields and methods. Is this correct ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
7
0 / 0

[JBoss JIRA] Created: (CDITCK-63) Test decorators and interceptors in other scopes than @Dependent

by Marius Bogoevici (JIRA)

Test decorators and interceptors in other scopes than @Dependent ---------------------------------------------------------------- Key: CDITCK-63 URL: https://jira.jboss.org/jira/browse/CDITCK-63 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Marius Bogoevici Prompted by https://jira.jboss.org/jira/browse/WELD-296 (at the time when the issue was reported decorators were not working correctly with client proxies). This is an implied assertion, but due to the complexity of the implementation, it is still desirable to see that the implementation handles it correctly. -- 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

12 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (CDITCK-172) Tests needed for transactional observers that initiate, commit or rollback transactions

by David Allen (JIRA)

Tests needed for transactional observers that initiate, commit or rollback transactions --------------------------------------------------------------------------------------- Key: CDITCK-172 URL: https://jira.jboss.org/browse/CDITCK-172 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.1.0.CR1 Reporter: David Allen Priority: Minor Tests for the following assertion can be implemented and require the container to provide its own UserTransaction to prohibit the calls from succeeding: 10.5 (bd) An observer method may not directly initiate, commit or rollback JTA transactions. At the moment, the specification does not really specify what happens if an observer method does make these calls. -- 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

12 years, 10 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2011