April 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1122) Calling a method on a removed EJB does not result in NoSuchEJBException

by Stuart Douglas (JIRA)

Stuart Douglas created WELD-1122: ------------------------------------ Summary: Calling a method on a removed EJB does not result in NoSuchEJBException Key: WELD-1122 URL: https://issues.jboss.org/browse/WELD-1122 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha2, 1.1.7.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.1.8.Final, 1.2.0.Beta1 Instead it just returns null -- 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
1
0 / 0

[JBoss JIRA] (CDITCK-270) TransactionalObserverTest.testSucessfullTransaction() unstable

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDITCK-270: -------------------------------------- Summary: TransactionalObserverTest.testSucessfullTransaction() unstable Key: CDITCK-270 URL: https://issues.jboss.org/browse/CDITCK-270 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.1.0.Alpha2 Reporter: Jozef Hartinger Assignee: Martin Kouba Fix For: TBC org.jboss.cdi.tck.tests.event.observer.transactional.TransactionalObserverTest.testSucessfullTransaction() seems to be failing randomly with java.lang.AssertionError: expected:<true> but was:<false> on line 48 I guess the following assertion is not valid since both "checkpoints" may be set in the same millisecond {code:JAVA} assertTrue(AccountTransactionObserver.beforeCompletionObservedTime > checkpoint); {code} -- 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

2
2
0 / 0

[JBoss JIRA] (CDITCK-266) Provide the porting package javadoc as part of the CDI TCK bundle

by Martin Kouba (JIRA)

Martin Kouba created CDITCK-266: ----------------------------------- Summary: Provide the porting package javadoc as part of the CDI TCK bundle Key: CDITCK-266 URL: https://issues.jboss.org/browse/CDITCK-266 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.0.5.CR1, 1.1.0.Alpha2 -- 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
1
0 / 0

[JBoss JIRA] (WELD-1069) Parallelize Weld bootstrap

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1069: ------------------------------------- Summary: Parallelize Weld bootstrap Key: WELD-1069 URL: https://issues.jboss.org/browse/WELD-1069 Project: Weld Issue Type: Task Affects Versions: 2.0.0.Alpha1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Blocker Fix For: 2.0.0.Alpha2 -- 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
2
0 / 0

[JBoss JIRA] (WELD-1114) Remaining Weld references after WAR undeployement

by Tomas Remes (JIRA)

Tomas Remes created WELD-1114: --------------------------------- Summary: Remaining Weld references after WAR undeployement Key: WELD-1114 URL: https://issues.jboss.org/browse/WELD-1114 Project: Weld Issue Type: Enhancement Components: Bootstrap and Metamodel API Affects Versions: 1.1.7.Final Environment: JBoss AS 7.1.1.Final, JProfiler Reporter: Tomas Remes Attachments: weld-deployment-test.jps I am not sure that this can be considered as issue, but when you run JBoss AS in JProfiler and try to deploy and undeploy simple Weld Web application (for example numberguess), you can find some referenced Weld classes in JProfiler even after performing GC. For example WeldBootstrap class, which has incoming references in following order: {noformat} ... -> org.jboss.msc.service.ServiceControllerImpl -> org.jboss.msc.value.ImmediateValue -> org.jboss.as.weld.service.WeldService -> org.jboss.as.weld.WeldContainer -> org.jboss.weld.bootstrap.WeldBootstrap {noformat} JProfiler snapshot is in attachement. In JProfiler you can filter org.jboss.weld.bootstrap classes and by right clicking you can show selection in Heap Walker, where you can also find references graph or tree. -- 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
1
0 / 0

[JBoss JIRA] (WELD-51) Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WELD-51?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated WELD-51: -------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl > ----------------------------------------------------------------------------------------- > > Key: WELD-51 > URL: https://issues.jboss.org/browse/WELD-51 > Project: Weld > Issue Type: Feature Request > Components: Reflection layer > Reporter: Pete Muir > Assignee: Jozef Hartinger > Priority: Critical > Fix For: 2.0.0.Alpha3 > > -- 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-1049) BeanManager.createInjectionTarget() does not support interception

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1049: ------------------------------------- Summary: BeanManager.createInjectionTarget() does not support interception Key: WELD-1049 URL: https://issues.jboss.org/browse/WELD-1049 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Ales Justin Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 SimpleInjectionTarget does not have support for interceptors nor decorators. -- 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

2
4
0 / 0

[JBoss JIRA] (CDITCK-268) There should be some tests for decorating session beans

by Stuart Douglas (JIRA)

Stuart Douglas created CDITCK-268: ------------------------------------- Summary: There should be some tests for decorating session beans Key: CDITCK-268 URL: https://issues.jboss.org/browse/CDITCK-268 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Stuart Douglas At the moment it looks like there are no tests for decoration of session beans, either in the weld code base or the TCK. I think we need to test the following: - Basic decoration - Ordering (should run inside interceptors) - Decoration of non-contextual instances -- 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

2
3
0 / 0

[JBoss JIRA] (WELD-1108) Bean with a @Named stereotype is not injected into a @Named injection point

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created WELD-1108: ------------------------------------------- Summary: Bean with a @Named stereotype is not injected into a @Named injection point Key: WELD-1108 URL: https://issues.jboss.org/browse/WELD-1108 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Affects Versions: 1.1.5.Final Reporter: Viacheslav Kabanovich 1. Create a stereotype @MyStereotype annotated @Named. 2. Create a bean class test.MyBean annotated @MyStereotype. Now, there is EL name 'myBean' available. 3. Create, in another class bean, an injection point @Inject @Named MyBean myBean. 4. Deploy the application Error: WELD-001408 Unsatisfied dependencies for type [MyBean] with qualifiers [@Named] at injection point [[field] @Named @Inject test.AnotherBean.myBean] 5. Add @Named to test.MyBean and deploy the application again. Success. I am not sure if it is a bug. Section 5.2. "Typesafe resolution" says that in order to be injected, the bean should have all the required qualifiers, and @Named is a required qualifier at the injection point 'myBean'. The question is, can we consider that a bean has qualifier @Named if it is annotated by a @Named stereotype? I could not find a plain statement in JSR-299 on that. However, if a stereotype A declares another stereotype B, a bean annotated with A is as good as one annotated with both A and B (section 2.7.5.1. says 'stereotype declarations are transitive'); and annotation @Named added to a stereotype A gives EL name to a bean annotated with A, as if it is annotated with @Named explicitly. Is it enough to answer 'yes' to the question above, or is it a 'jumping to conclusions' case? -- 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

3
2
0 / 0

[JBoss JIRA] (WELD-1106) Default name for a managed bean is not correct for class name that starts with two or more upper case letters

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created WELD-1106: ------------------------------------------- Summary: Default name for a managed bean is not correct for class name that starts with two or more upper case letters Key: WELD-1106 URL: https://issues.jboss.org/browse/WELD-1106 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Affects Versions: 1.1.5.Final Reporter: Viacheslav Kabanovich "3.1.5. Default name for a managed bean The default name for a managed bean is the unqualified class name of the bean class, after converting the first character to lower case." For a class named XBean, default name of a managed bean should be xBean. However, in runtime with Weld 1.1.5, this name is not available in EL, instead name XBean is available. -- 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

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2012