August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Updated: (WELD-85) Performance and Scalability regression testing

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-85?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-85: -------------------------- Fix Version/s: 1.1.0.BETA2 (was: 1.1.0.BETA1) > Performance and Scalability regression testing > ---------------------------------------------- > > Key: WELD-85 > URL: https://jira.jboss.org/browse/WELD-85 > Project: Weld > Issue Type: Sub-task > Reporter: Pete Muir > Fix For: 1.1.0.BETA2 > > > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-485) ProcessAnnotatedType event should be run for types added through BeforeBeanDiscovery.addAnnotatedType

by Stuart Douglas (JIRA)

ProcessAnnotatedType event should be run for types added through BeforeBeanDiscovery.addAnnotatedType ----------------------------------------------------------------------------------------------------- Key: WELD-485 URL: https://jira.jboss.org/jira/browse/WELD-485 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Stuart Douglas Fix For: 1.0.2.CR1 -- 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, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (WELD-382) Move all classes which can be accessed by an integration to the SPI

by Pete Muir (JIRA)

Move all classes which can be accessed by an integration to the SPI ------------------------------------------------------------------- Key: WELD-382 URL: https://jira.jboss.org/jira/browse/WELD-382 Project: Weld Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.1.CR1 If it is required to have a class instance, options are to either reference the class name or delegate via reflection. Both are a bit eugh. Another option is to annotate the internal class and have a compiler plugin which picks up if it is moved. -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-585) org.jboss.weld.util.reflection.Reflections.isAssignableFrom(Class<?>, Type[], Class<?>, Type[]) should require equal rawType

by Pete Muir (JIRA)

org.jboss.weld.util.reflection.Reflections.isAssignableFrom(Class<?>, Type[], Class<?>, Type[]) should require equal rawType ---------------------------------------------------------------------------------------------------------------------------- Key: WELD-585 URL: https://jira.jboss.org/browse/WELD-585 Project: Weld Issue Type: Bug Components: Reflection layer Reporter: Pete Muir Priority: Critical Fix For: 1.1.0.BETA1 Otherwise we end up with incorrect actual type argument comparisons (parameter order can change between supertypes) -- 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

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-455) @Observes(notifyObserver=IF_EXISTS) should be @Observes(receive=IF_EXISTS)

by Matthieu Chase Heimer (JIRA)

@Observes(notifyObserver=IF_EXISTS) should be @Observes(receive=IF_EXISTS) -------------------------------------------------------------------------- Key: WELD-455 URL: https://jira.jboss.org/jira/browse/WELD-455 Project: Weld Issue Type: Bug Components: CDI API, Events Affects Versions: 1.0.1.Final Environment: Windows XP SP3, NetBeans 6.8, GlassFish v3 Reporter: Matthieu Chase Heimer @Observes has an element named "notifyObserver" of type javax.enterprise.event.Reception but the name should be "receive". See page 75 of the CDI spec, 10.4.3. Conditional observer methods. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-583) Transactional observer Arquillian tests will not deploy on JBoss AS

by David Allen (JIRA)

Transactional observer Arquillian tests will not deploy on JBoss AS ------------------------------------------------------------------- Key: WELD-583 URL: https://jira.jboss.org/browse/WELD-583 Project: Weld Issue Type: Bug Reporter: David Allen The test in org.jboss.weld.tests.event.observer.transactional.TransactionalObserversTest does not deploy properly in JBoss AS and the actual cause of the problem is masked by another error Arquillian makes during undeploy as a result of the exception. -- 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

14 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-561) Not intuitive error message: WELD-000069 An interceptor must have at least one binding, but Foo has none

by Marcin Zajaczkowski (JIRA)

Not intuitive error message: WELD-000069 An interceptor must have at least one binding, but Foo has none -------------------------------------------------------------------------------------------------------- Key: WELD-561 URL: https://jira.jboss.org/browse/WELD-561 Project: Weld Issue Type: Task Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Marcin Zajaczkowski Priority: Trivial WELD-000069 error message (without debug message) is not very intuitive. DEBUG org.jboss.weld.Reflection - WELD-000602 interface net.sf.perf4cdi.api.Perf4jProfiled is not declared @Target(TYPE, METHOD) or @Target(TYPE) ERROR org.jboss.weld.exceptions.DeploymentException: WELD-000069 An interceptor must have at least one binding, but net.sf.perf4cdi.Perf4jProfiledInterceptor has none at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:71) at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:55) at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:255) at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:106) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:151) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:377) at org.jboss.weld.mock.MockServletLifecycle.beginApplication(MockServletLifecycle.java:121) at org.jboss.weld.mock.TestContainer.startContainer(TestContainer.java:85) at org.jboss.weld.test.harness.AbstractStandaloneContainersImpl.deploy(AbstractStandaloneContainersImpl.java:40) at org.jboss.testharness.AbstractTest.deployArtifact(AbstractTest.java:103) at org.jboss.testharness.AbstractTest.beforeClass(AbstractTest.java:206) at org.jboss.weld.test.AbstractWeldTest.beforeClass(AbstractWeldTest.java:57) -- 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

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (WELD-544) Use org.jboss.spec.javax.interceptor instead of the current Interceptors 1.1 API artifact

by Marius Bogoevici (JIRA)

Use org.jboss.spec.javax.interceptor instead of the current Interceptors 1.1 API artifact ----------------------------------------------------------------------------------------- Key: WELD-544 URL: https://jira.jboss.org/browse/WELD-544 Project: Weld Issue Type: Feature Request Components: Infrastructure Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Priority: Critical Fix For: 1.0.2.CR1 -- 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

14 years, 4 months

2
5
0 / 0

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

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/CDITCK-16?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed CDITCK-16. --------------------------- Assignee: David Allen > Tests for transactional observers are inconsistent > -------------------------------------------------- > > Key: CDITCK-16 > URL: https://jira.jboss.org/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 > Assignee: 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-94) Route serialization/deserialization through SPI

by Pete Muir (JIRA)

Route serialization/deserialization through SPI ----------------------------------------------- Key: CDITCK-94 URL: https://jira.jboss.org/jira/browse/CDITCK-94 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.1.0.CR1 This allows a porting package to mirror the behavior of an app server which may provide special behavior here. -- 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, 4 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010