October 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Updated: (WELD-92) Unify asynchronous execution interfaces

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-92?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-92: -------------------------- Component/s: Events Infrastructure > Unify asynchronous execution interfaces > --------------------------------------- > > Key: WELD-92 > URL: https://jira.jboss.org/jira/browse/WELD-92 > Project: Weld > Issue Type: Feature Request > Components: Events, Infrastructure > Affects Versions: 1.0.0.BETA1 > Reporter: David Allen > Assignee: David Allen > Priority: Minor > Fix For: 1.1.0.BETA1 > > > Since the spec identifies several cases of asynchronous tasks which must be performed, the RI should have a single, consistent set of interfaces to provide the executor services needed and the tasks to be performed. In Java SE 5 and 6, java.util.concurrent does provide useful interfaces for dealing with tasks which are executed by a separate service. It is recommended that the Executor interface be used as-is for those not requiring a timer (just execution in a separate thread of control), and perhaps the Delayed mix-in style interface for tasks requiring a timer or delay of execution. Alternatively, another executor interface can be chosen from SE to provide methods which take both the task to perform and the time delay. > In general, use of the java.util.concurrent interfaces, and even the implementations where possible, will reduce the amount of code in the RI and make better use of existing Java resources. -- 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: (WELD-30) JBoss Runs WebBeans Example Apps With GlassFish

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-30?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-30: -------------------------- Fix Version/s: 1.0.0.CR2 Priority: Critical (was: Major) > JBoss Runs WebBeans Example Apps With GlassFish > ----------------------------------------------- > > Key: WELD-30 > URL: https://jira.jboss.org/jira/browse/WELD-30 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish > Reporter: Roger Kitain > Assignee: Roger Kitain > Priority: Critical > Fix For: 1.0.0.CR2 > > > JBoss runs WebBeans example applications with GlassFish. -- 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: (WELD-56) Supporting proxies with no no-arg constructors

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-56?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-56: -------------------------- Fix Version/s: 1.1.0.BETA1 > Supporting proxies with no no-arg constructors > ---------------------------------------------- > > Key: WELD-56 > URL: https://jira.jboss.org/jira/browse/WELD-56 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.1.0.BETA1 > > > On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene > <jason.greene(a)redhat.com> wrote: > Hi Everyone, > As a non-standard extension, I was thinking that we could support generation > proxies of classes not containing no-arg constructors by using various > techniques that are supported by most JDKs. > This would involve generating a proxy with a constructor call passing bogus > parameters. Then a JDK specific approach would be used to instantiate the > proxy class: > Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient > Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- 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: (WELD-92) Unify asynchronous execution interfaces

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-92?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-92: -------------------------- Fix Version/s: 1.1.0.BETA1 > Unify asynchronous execution interfaces > --------------------------------------- > > Key: WELD-92 > URL: https://jira.jboss.org/jira/browse/WELD-92 > Project: Weld > Issue Type: Feature Request > Affects Versions: 1.0.0.BETA1 > Reporter: David Allen > Assignee: David Allen > Priority: Minor > Fix For: 1.1.0.BETA1 > > > Since the spec identifies several cases of asynchronous tasks which must be performed, the RI should have a single, consistent set of interfaces to provide the executor services needed and the tasks to be performed. In Java SE 5 and 6, java.util.concurrent does provide useful interfaces for dealing with tasks which are executed by a separate service. It is recommended that the Executor interface be used as-is for those not requiring a timer (just execution in a separate thread of control), and perhaps the Delayed mix-in style interface for tasks requiring a timer or delay of execution. Alternatively, another executor interface can be chosen from SE to provide methods which take both the task to perform and the time delay. > In general, use of the java.util.concurrent interfaces, and even the implementations where possible, will reduce the amount of code in the RI and make better use of existing Java resources. -- 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] Closed: (WELD-55) @Named beans cannot be injected

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-55?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-55. ------------------------- Fix Version/s: 1.0.0.CR1 Resolution: Done Assignee: Pete Muir > @Named beans cannot be injected > ------------------------------- > > Key: WELD-55 > URL: https://jira.jboss.org/jira/browse/WELD-55 > Project: Weld > Issue Type: Bug > Components: Resolution (Typesafe and by Name) > Affects Versions: 1.0.0.PREVIEW1 > Reporter: Shane Bryzak > Assignee: Pete Muir > Fix For: 1.0.0.CR1 > > > To reproduce, annotate the org.jboss.jsr299.tck.tests.lookup.injection.Fox class in the TCK with @Named. -- 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: (WELD-87) Perform load testing for scalability hotspots

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-87?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-87: -------------------------- Fix Version/s: 1.0.1.CR1 > Perform load testing for scalability hotspots > --------------------------------------------- > > Key: WELD-87 > URL: https://jira.jboss.org/jira/browse/WELD-87 > Project: Weld > Issue Type: Sub-task > Reporter: Pete Muir > Fix For: 1.0.1.CR1 > > > Grouping issue for suspected scalability hotspots -- 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: (WELD-85) Performance and Scalability regression testing

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-85?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-85: -------------------------- Fix Version/s: 1.0.1.CR1 > Performance and Scalability regression testing > ---------------------------------------------- > > Key: WELD-85 > URL: https://jira.jboss.org/jira/browse/WELD-85 > Project: Weld > Issue Type: Sub-task > Reporter: Pete Muir > Fix For: 1.0.1.CR1 > > > Create some basic performance and scalability testing which can run in a continuous integration environment and report improvements or regressions over time -- 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: (WELD-91) Document a strategy for writing a unit test which guards against performance blackspots reoccurring

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-91?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-91: -------------------------- Fix Version/s: 1.0.1.CR1 > Document a strategy for writing a unit test which guards against performance blackspots reoccurring > --------------------------------------------------------------------------------------------------- > > Key: WELD-91 > URL: https://jira.jboss.org/jira/browse/WELD-91 > Project: Weld > Issue Type: Task > Reporter: Pete Muir > Fix For: 1.0.1.CR1 > > > When someone reports/isolates a performance issue, we need to write a unit test to stop it reoccurring (a regression occurring). -- 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: (WELD-86) Perform profiling for performance hotspots

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-86?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-86: -------------------------- Fix Version/s: 1.0.1.CR1 > Perform profiling for performance hotspots > ------------------------------------------ > > Key: WELD-86 > URL: https://jira.jboss.org/jira/browse/WELD-86 > Project: Weld > Issue Type: Sub-task > Reporter: Pete Muir > Fix For: 1.0.1.CR1 > > > Grouping issue for suspected performance hotspots -- 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-8) Use case based tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-8?page=com.atlassian.jira.plugi... ] Pete Muir updated CDITCK-8: --------------------------- Component/s: Tests > Use case based tests > -------------------- > > Key: CDITCK-8 > URL: https://jira.jboss.org/jira/browse/CDITCK-8 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Priority: Critical > Fix For: 1.1.0.CR1 > > > The TCK should contain at least one larger test - like the number guess example tests -- 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