September 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-522) Weld makes my Java SE app startup time >100x slower

by Morten Christensen (JIRA)

Weld makes my Java SE app startup time >100x slower ---------------------------------------------------- Key: WELD-522 URL: https://jira.jboss.org/jira/browse/WELD-522 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Java 6, Weld 1.01 SE + lots of jars on the classpath Reporter: Morten Christensen Booting my Java SE app without weld takes << 1s BUT the 1 line for initializing weld to autowire my app takes at least 4-5 seconds. My app is not so big and consist of ~20-30 singletons that must be wired + various other non-weld stuff. I have lots of stuff on my classpath so I suspect that could be why weld is going crazy. I guess this could be improved if I can have weld limited to work only inside my own jar and/or only work with specific classes/packages. P.S. With breakpoints enabled in a debugger and a bit of unluck, I was even able to have welds initialization to take ~ 5 minutes one day (reduced to seconds again after I removed all breakpoints though). -- 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

13 years, 5 months

3
14
0 / 0

[JBoss JIRA] Created: (WELD-405) Add manual verification process for GAE support to QA guide

by Pete Muir (JIRA)

Add manual verification process for GAE support to QA guide ----------------------------------------------------------- Key: WELD-405 URL: https://jira.jboss.org/jira/browse/WELD-405 Project: Weld Issue Type: Feature Request Components: Class Beans (Managed and Session) Reporter: Pete Muir Assignee: Shane Bryzak Fix For: 1.0.1.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

13 years, 5 months

1
11
0 / 0

[JBoss JIRA] Created: (WELD-211) Tests which exercise an SPI implementation

by Pete Muir (JIRA)

Tests which exercise an SPI implementation ------------------------------------------ Key: WELD-211 URL: https://jira.jboss.org/jira/browse/WELD-211 Project: Weld Issue Type: Feature Request Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Pete Muir Fix For: 1.0.1.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

13 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (WELD-437) Use subclasses for interceptors and decorators

by Pete Muir (JIRA)

Use subclasses for interceptors and decorators ---------------------------------------------- Key: WELD-437 URL: https://jira.jboss.org/jira/browse/WELD-437 Project: Weld Issue Type: Bug Reporter: Pete Muir 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-137) org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest ------------------------------------------------------------------------------------------------------- Key: CDITCK-137 URL: https://jira.jboss.org/jira/browse/CDITCK-137 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Method : testChainedDecoratorInvocation In this test, TCK tests the injection points of the Decortor delegate. But it seems that this test is specific to Weld. In our case, we manage decorator stack via single delegate not via injection each decorator reference to DecoratorInvocationTest -- 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

13 years, 6 months

3
22
0 / 0

[JBoss JIRA] Created: (CDITCK-180) org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public

by Lance Andersen (JIRA)

org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-180 URL: https://jira.jboss.org/browse/CDITCK-180 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.Final Reporter: Lance Andersen The following two classes are missing public in there declarations: org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard Specification version & section: The EJB Spec states the following in section "4.9.2 Session Bean Class": The class must be defined as public, must not be final, and must not be abstract. The class must be a top level class. This clearly violates that rule. These classes are not public. Tests Affected: testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean testSpecializingBeanHasNameOfSpecializedBean from org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest Output: [9/7/10 14:57:34:309 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract [9/7/10 14:57:34:312 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract -- 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

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-178) DecoratorDefinitionTest.testDecoratedTypes() asserts that a superinterface of the decorator bean class is not a decorated type.

by Alexey Kazakov (JIRA)

DecoratorDefinitionTest.testDecoratedTypes() asserts that a superinterface of the decorator bean class is not a decorated type. ------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-178 URL: https://jira.jboss.org/browse/CDITCK-178 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Alexey Kazakov See public void testDecoratedTypes() { List<Decorator<?>> decorators = getCurrentManager().resolveDecorators(FooBar.TYPES); assert decorators.size() == 1; assert decorators.get(0).getDecoratedTypes().size() == 3; assert decorators.get(0).getDecoratedTypes().contains(Foo.class); assert decorators.get(0).getDecoratedTypes().contains(Bar.class); assert decorators.get(0).getDecoratedTypes().contains(Baz.class); assert !decorators.get(0).getDecoratedTypes().contains(Serializable.class); assert !decorators.get(0).getDecoratedTypes().contains(FooDecorator.class); assert !decorators.get(0).getDecoratedTypes().contains(AbstractFooDecorator.class); assert !decorators.get(0).getDecoratedTypes().contains(Boo.class); } But Boo is a superinterface of FooDecorator (not a superclass). And according of JSR-299 8.1 it's a decorated type: 8.1. Decorator beans A decorator is a managed bean. The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for java.io.Serializable. -- 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

13 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (CDITCK-182) Challenging the expected behaviour of SessionBeanPolicyTest in a hierarchical deployment

by Marius Bogoevici (JIRA)

Challenging the expected behaviour of SessionBeanPolicyTest in a hierarchical deployment ---------------------------------------------------------------------------------------- Key: CDITCK-182 URL: https://jira.jboss.org/browse/CDITCK-182 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.2.CR2 Reporter: Marius Bogoevici Fix For: 1.0.2.CR3 Test in cause: org.jboss.jsr299.tck.tests.policy.enterprise.SessionBeanPolicyTest The expectation is that EnabledEjb will be enabled, since it is enabled as an alternative in jar's beans.xml. However, the resolution in the test is done based on the BeanManager settings of the WAR that runs the test (in which said bean is not enabled as an alternative). -- 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

13 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (CDITCK-138) org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest ------------------------------------------------------------------- Key: CDITCK-138 URL: https://jira.jboss.org/jira/browse/CDITCK-138 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu In the testIsDelegateMethod(), assert cat.getInjectionPoint().isDelegate(); But Cat injection point is not decorator delegate point. -- 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

13 years, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (CDITCK-181) Tests try to use beanManager.getContext() to get a scope they know is inactive

by Pete Muir (JIRA)

Tests try to use beanManager.getContext() to get a scope they know is inactive ------------------------------------------------------------------------------ Key: CDITCK-181 URL: https://jira.jboss.org/browse/CDITCK-181 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3 org.jboss.jsr299.tck.tests.lookup.clientProxy.ClientProxyTest.testInactiveScope() org.jboss.jsr299.tck.tests.event.EventTest.testStaticObserverMethodInvoked() -- 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

13 years, 6 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues September 2010