February 2012 - weld-issues - Jboss List Archives

[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, 2 months

3
5
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, 2 months

4
6
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, 2 months

3
3
0 / 0

[JBoss JIRA] (WELD-1066) Introduce an optional "global enablement" mode

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1066: ------------------------------------- Summary: Introduce an optional "global enablement" mode Key: WELD-1066 URL: https://issues.jboss.org/browse/WELD-1066 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: TBC https://issues.apache.org/jira/browse/DELTASPIKE-61 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (WELD-1048) Decorated dependent bean not passivation capable

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1048: ------------------------------------- Summary: Decorated dependent bean not passivation capable Key: WELD-1048 URL: https://issues.jboss.org/browse/WELD-1048 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Ales Justin Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 {code} java.io.NotSerializableException: org.jboss.weld.injection.OnDemandBeanInstance at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] (WELD-1043) Convert Weld example ftests to Ajocado

by Marek Schmidt (Created) (JIRA)

Convert Weld example ftests to Ajocado -------------------------------------- Key: WELD-1043 URL: https://issues.jboss.org/browse/WELD-1043 Project: Weld Issue Type: Feature Request Components: Examples Affects Versions: 1.1.5.Final Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: 1.2.0.Beta1 ... so we can use ContainerController for the clustering tests (WELD-266) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] (WELD-1061) Inconsistent results from BeanManager.getBeans(Type, Annotation .. ) after AfterBeanDiscovery event

by Marko Milenković (JIRA)

Marko Milenković created WELD-1061: -------------------------------------- Summary: Inconsistent results from BeanManager.getBeans(Type, Annotation .. ) after AfterBeanDiscovery event Key: WELD-1061 URL: https://issues.jboss.org/browse/WELD-1061 Project: Weld Issue Type: Bug Components: Weld SPI Affects Versions: 1.1.5.Final Environment: fedora core 14 linux 32b, windows vista 32b Reporter: Marko Milenković scenario to reproduce the incostencies: * create a simple CDI project and a class, lets name it SimpleClass * create a simple CDI extension and inject BeanManager in it * create observer method for AfterBeanDiscovery and AfterDeploymentValidation lifecycle events * beanManager.getBeans(SimpleClass.class) returns 0 results if called in AfterBeanDiscovery observer method * beanManager.getBeans(SimpleClass.class) returns 1 results if called in AfterDeploymentValidation observer method * beanManager.getBeans(Object.class) returns correct results in both cases Looks like that BeanManager doesn't have correct bean types after AfterBeanDiscovery phase. I can't find any details about this behaviour in JSR299. weld and weld-core version is 1.1.5.Final scenario project: https://github.com/milenkovicm/examples/tree/master/weld -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
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, 3 months

6
7
0 / 0

[JBoss JIRA] (CDITCK-12) Test injection of paramterized types, not just lookup via manager

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDITCK-12?page=com.atlassian.jira.plugin.... ] Martin Kouba resolved CDITCK-12. -------------------------------- Assignee: Martin Kouba Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.CR1) Resolution: Done See tests in *org.jboss.cdi.tck.tests.lookup.injection.parameterized* package. > Test injection of paramterized types, not just lookup via manager > ----------------------------------------------------------------- > > Key: CDITCK-12 > URL: https://issues.jboss.org/browse/CDITCK-12 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Martin Kouba > Priority: Minor > Fix For: 1.1.0.Alpha2 > > > We currently don't test the injection code for paramterized types, just TypeLiteral lookup... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDITCK-261) Update CDI TCK documentation

by Martin Kouba (Created) (JIRA)

Update CDI TCK documentation ---------------------------- Key: CDITCK-261 URL: https://issues.jboss.org/browse/CDITCK-261 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2012