March 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1096) Observing an array fails randomly

by Ales Justin (JIRA)

Ales Justin created WELD-1096: --------------------------------- Summary: Observing an array fails randomly Key: WELD-1096 URL: https://issues.jboss.org/browse/WELD-1096 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.1.6.Final Reporter: Ales Justin Assignee: Marko Lukša Fix For: 1.2.0.Beta1 See forum and pull-request for more info. -- 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

1
2
0 / 0

[JBoss JIRA] (WELD-1) Add tests for multiple wars in an ear

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.sys... ] SBS JIRA Integration updated WELD-1: ------------------------------------ Forum Reference: https://community.jboss.org/message/721341#721341, https://community.jboss.org/message/653310#653310, https://community.jboss.org/message/717656#717656 (was: https://community.jboss.org/message/721341#721341, https://community.jboss.org/message/717656#717656) > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://issues.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.2.0.Beta1 > > > This is a typical area of weakness in Seam etc. due to misuse of singletons etc. > Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak. -- 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

1
0
0 / 0

[JBoss JIRA] (WELD-1) Add tests for multiple wars in an ear

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.sys... ] SBS JIRA Integration updated WELD-1: ------------------------------------ Forum Reference: https://community.jboss.org/message/721341#721341, https://community.jboss.org/message/717656#717656 (was: https://community.jboss.org/message/717656#717656) > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://issues.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.2.0.Beta1 > > > This is a typical area of weakness in Seam etc. due to misuse of singletons etc. > Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak. -- 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

1
0
0 / 0

[JBoss JIRA] (WELD-1) Add tests for multiple wars in an ear

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.sys... ] SBS JIRA Integration updated WELD-1: ------------------------------------ Forum Reference: https://community.jboss.org/message/717656#717656 > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://issues.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.2.0.Beta1 > > > This is a typical area of weakness in Seam etc. due to misuse of singletons etc. > Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak. -- 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

1
0
0 / 0

[JBoss JIRA] (WELD-1) Add tests for multiple wars in an ear

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.sys... ] SBS JIRA Integration updated WELD-1: ------------------------------------ Forum Reference: https://community.jboss.org/message/721341#721341, https://community.jboss.org/message/717656#717656 (was: https://community.jboss.org/message/721341#721341, https://community.jboss.org/message/717656#717656) > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://issues.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.2.0.Beta1 > > > This is a typical area of weakness in Seam etc. due to misuse of singletons etc. > Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak. -- 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

1
0
0 / 0

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

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDITCK-15?page=com.atlassian.jira.plugin.... ] Martin Kouba resolved CDITCK-15. -------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.CR1) Resolution: Done > Corner case tests for injecting into non-contextual EJBs > -------------------------------------------------------- > > Key: CDITCK-15 > URL: https://issues.jboss.org/browse/CDITCK-15 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Martin Kouba > Fix For: 1.1.0.Alpha2 > > > 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, 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, 1 month

1
0
0 / 0

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

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDITCK-15?page=com.atlassian.jira.plugin.... ] Martin Kouba reassigned CDITCK-15: ---------------------------------- Assignee: Martin Kouba (was: Shane Bryzak) > Corner case tests for injecting into non-contextual EJBs > -------------------------------------------------------- > > Key: CDITCK-15 > URL: https://issues.jboss.org/browse/CDITCK-15 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Martin Kouba > 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, 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, 1 month

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDITCK-15?page=com.atlassian.jira.plugin.... ] Pete Muir commented on CDITCK-15: --------------------------------- For example, check that: {code} @Stateful @RequestScoped class Bar { @Inject Baz baz; public Baz getBaz() { return baz; } } {code} {code} @Stateful @RequestScoped class Baz { @Inject Bar bar; public Bar getBar() { return bar; } } {code} And verify that this works, assuming they are normal scoped of course! > Corner case tests for injecting into non-contextual EJBs > -------------------------------------------------------- > > Key: CDITCK-15 > URL: https://issues.jboss.org/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, 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, 1 month

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDITCK-15?page=com.atlassian.jira.plugin.... ] Pete Muir commented on CDITCK-15: --------------------------------- For example, check that: {code} class Foo {} {code} {code} @Stateless class Bar { @Inject Foo foo; public Foo getFoo() { return foo; } } {code} {code} @Stateless class Baz { @EJB Bar bar; public Bar getBar() { return bar; } } {code} {code} @Stateless class Qux { @EJB Baz baz; public Baz getBaz() { return baz; } } {code} {code} assertNotNull(qux.getBaz().getBar()); {code} > Corner case tests for injecting into non-contextual EJBs > -------------------------------------------------------- > > Key: CDITCK-15 > URL: https://issues.jboss.org/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, 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WELD-13) Use the builder pattern to create Bean objects

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/WELD-13?page=com.atlassian.jira.plugin.sy... ] Ales Justin updated WELD-13: ---------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.6.Final) > Use the builder pattern to create Bean objects > ---------------------------------------------- > > Key: WELD-13 > URL: https://issues.jboss.org/browse/WELD-13 > Project: Weld > Issue Type: Feature Request > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Assignee: Stuart Douglas > Priority: Critical > Fix For: 1.2.0.Beta1 > > > Currently we create the Bean objects using a two phase initialization, partly via the constructor, and partly via an initialize() method, this allows us to create the beans, attach them to the bean manager and then do further work once all bean objects exist. This has a number of problems: > 1) objects are not fully immutable which means we rely on developers ability to keep them effectively immutable > 2) the objects are a mess of init methods and getters > 3) creation logic is convoluted > It would be far better to create builders (or factories) that can create the beans as needed, this will cleanly split out the creation logic from the bean object, and allow us to create fully immutable objects, thus making it easier to verify the thread-safety of the code. > A side effect of this will be that we can't use two-phase initialization two set up certain stuff after all beans are present. To overcome this we will need to order the bean creation so that beans required by other beans are created first and thus can be attached as needed. > The rules I am aware of: > * producer methods and fields should be created after the class bean that declares them as they need to know that bean in order to be instantiated > * specialized beans need to be created in the order least specialized to most specialized as a more specialized bean needs to read the metadata of the less specialized bean -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2012