October 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Updated: (CDITCK-11) Test more corner cases for specialization

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-11?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-11: ---------------------------- Component/s: Tests > Test more corner cases for specialization > ----------------------------------------- > > Key: CDITCK-11 > URL: https://jira.jboss.org/jira/browse/CDITCK-11 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: David Allen > Priority: Minor > Fix For: 1.1.0.CR1 > > > For example: > * producer methods declared on enterprise beans > * instantiation tests only check direct specialization, should also test indirect specialization > * more complete tests for instantiation? -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-16) Tests for transactional observers are inconsistent

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-16?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-16: ---------------------------- Component/s: Tests > Tests for transactional observers are inconsistent > -------------------------------------------------- > > Key: CDITCK-16 > URL: https://jira.jboss.org/jira/browse/CDITCK-16 > Project: CDI TCK > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tests > Affects Versions: 1.0.0.Beta1 > Reporter: David Allen > Fix For: 1.1.0.CR1 > > Attachments: server.log > > > The tests use a single stateful session bean which has many observer methods defined. Each test fires a different type of event through a stateless session bean. All of the observer methods have been invoked with the correct state information stored according to logging information, but the tests are not always seeing the same state information. > The results of the tests are never random in any way, but they have changed over a period of a day or two with other changes to the TCK or RI. Any local changes to these tests that are innocuous still do not change the results in any way. The same set of tests are always inconsistent with the logging information on the same day. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-18) TCK should test both synchronous and asynchronous calls when verifying container requirements

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-18?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-18: ---------------------------- Component/s: Tests > TCK should test both synchronous and asynchronous calls when verifying container requirements > --------------------------------------------------------------------------------------------- > > Key: CDITCK-18 > URL: https://jira.jboss.org/jira/browse/CDITCK-18 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: David Allen > Fix For: 1.1.0.CR1 > > > For each test that verifies environment or other container requirements such as BeanManager functionality from a session bean, the same test should occur with both synchronous and asynchronous calls to verify that both always function. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-20) Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-20?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-20: ---------------------------- Component/s: Tests > Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event > --------------------------------------------------------------------------------------------------------------------------- > > Key: CDITCK-20 > URL: https://jira.jboss.org/jira/browse/CDITCK-20 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Fix For: 1.0.0.CR3 > > -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-19) Add a test verifying that @Current is inherited in specialization

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-19?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-19: ---------------------------- Component/s: Tests > Add a test verifying that @Current is inherited in specialization > ----------------------------------------------------------------- > > Key: CDITCK-19 > URL: https://jira.jboss.org/jira/browse/CDITCK-19 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Fix For: 1.0.0.CR3 > > > Given > class Bean1 { > } > @Binding1 > @Specializes > class Bean2 extends Bean1{ > } > verify that Bean2 has binding @Binding1 only > Given > @Binding1 > class Bean1 { > } > @Specializes > class Bean2 extends Bean1{ > } > verify that Bean2 has bindings @Current @Binding1 only > Given > @Binding2 > class Bean1 { > } > class Bean2 extends Bean1{ > } > @Binding2 is @Inherited > Verify that Bean2 has bindings @Binding2 only -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-15) Corner case tests for injecting into non-contextual EJBs

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-15?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-15: ---------------------------- Component/s: Tests > Corner case tests for injecting into non-contextual EJBs > -------------------------------------------------------- > > Key: CDITCK-15 > URL: https://jira.jboss.org/jira/browse/CDITCK-15 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Shane Bryzak > Fix For: 1.1.0.CR1 > > > For example: > * chains of EJBs with contextual instances > * reentrant injcetion (allowed by EJB?) -- 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

14 years, 6 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-12?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-12: ---------------------------- Component/s: Tests > Test injection of paramterized types, not just lookup via manager > ----------------------------------------------------------------- > > Key: CDITCK-12 > URL: https://jira.jboss.org/jira/browse/CDITCK-12 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Priority: Minor > Fix For: 1.1.0.CR1 > > > 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 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-4) Add tests for metadata overriding including EJBs

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-4?page=com.atlassian.jira.plugi... ] Pete Muir updated CDITCK-4: --------------------------- Component/s: Tests > Add tests for metadata overriding including EJBs > ------------------------------------------------ > > Key: CDITCK-4 > URL: https://jira.jboss.org/jira/browse/CDITCK-4 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Jozef Hartinger > Fix For: 1.0.0.CR3 > > -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-20) Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-20?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-20: ---------------------------- Fix Version/s: 1.0.0.CR3 > Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event > --------------------------------------------------------------------------------------------------------------------------- > > Key: CDITCK-20 > URL: https://jira.jboss.org/jira/browse/CDITCK-20 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Pete Muir > Fix For: 1.0.0.CR3 > > -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDITCK-18) TCK should test both synchronous and asynchronous calls when verifying container requirements

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-18?page=com.atlassian.jira.plug... ] Pete Muir updated CDITCK-18: ---------------------------- Fix Version/s: 1.1.0.CR1 > TCK should test both synchronous and asynchronous calls when verifying container requirements > --------------------------------------------------------------------------------------------- > > Key: CDITCK-18 > URL: https://jira.jboss.org/jira/browse/CDITCK-18 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David Allen > Fix For: 1.1.0.CR1 > > > For each test that verifies environment or other container requirements such as BeanManager functionality from a session bean, the same test should occur with both synchronous and asynchronous calls to verify that both always function. -- 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

14 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2009