January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDINT-37) Context not propagated to event observer

by Pete Muir (JIRA)

Context not propagated to event observer ---------------------------------------- Key: WELDINT-37 URL: https://jira.jboss.org/jira/browse/WELDINT-37 Project: Weld Integration Issue Type: Bug Components: JBoss EJB 3.0 integration Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.2.0.Beta6 See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testTransactionalObserverNotifiedImmediatelyWhenNoTransactionInProgress() -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (WELDINT-33) Servlet injection not working when app is deployed as an EAR

by Pete Muir (JIRA)

Servlet injection not working when app is deployed as an EAR ------------------------------------------------------------ Key: WELDINT-33 URL: https://jira.jboss.org/jira/browse/WELDINT-33 Project: Weld Integration Issue Type: Bug Components: Non-contextual injection Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.2.0.Beta6 -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (WELDINT-29) Add deployers for injection between Weld and MC

by Kabir Khan (JIRA)

Add deployers for injection between Weld and MC ----------------------------------------------- Key: WELDINT-29 URL: https://jira.jboss.org/jira/browse/WELDINT-29 Project: Weld Integration Issue Type: Feature Request Components: Deployer Reporter: Kabir Khan Assignee: Pete Muir Fix For: 5.2.0.Beta5 On 10 Nov 2009, at 10:39, Kabir Khan wrote: Hi Pete, I've done a fair bit of work on https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer which I need to commit. This falls into two parts. 1) Moving some of the hardcoded strings created by the deployers into DeployersUtils utility methods 2) New stuff for mc-weld integration I know you guys are busy releasing everything and don't want to fuck things up for you. So first of all, is there a code freeze on this repository at the moment? <pete>No code freeze officially. I did a new release of weld-int last night with the latest Weld 1.0.0 code. If you could hold until later today, so I can verify all, that would be great :-)</pete> Secondly, it looks like the AS 5.2 releases are taken from trunk? <pete>Yes.</pete> The stuff for 1) is pretty trivial. Apart from those the changes for 2) are all new classes, but this depends on snapshot versions of MC kernel and deployers. Unless you have any objections or better suggestions, I think I will create a new module for my 2) work which hardcodes the dependencies to those snapshot versions and which is excluded from the main build unless run with a special profile untill we have some proper MC releases. <pete>Yes, quite happy with that!</pete> -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDINT-26) Correctly extract exception message from Tomcat

by Pete Muir (JIRA)

Correctly extract exception message from Tomcat ----------------------------------------------- Key: WELDINT-26 URL: https://jira.jboss.org/jira/browse/WELDINT-26 Project: Weld Integration Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir org.jboss.jsr299.tck.tests.lookup.injectionpoint.broken.not.bean.InjectionPointTest -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (CDITCK-67) test applications failed to deploy due to "unresolvable ambiguous EL name exists"

by Hong Zhang (JIRA)

test applications failed to deploy due to "unresolvable ambiguous EL name exists" --------------------------------------------------------------------------------- Key: CDITCK-67 URL: https://jira.jboss.org/jira/browse/CDITCK-67 Project: CDI TCK Issue Type: CTS Challenge Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Environment: Ubuntu/X86 Reporter: Hong Zhang Priority: Critical I am investigation the test failures for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest class. The deployment failed for the application due to some validation failure in weld RI code. >From the stack trace, it found two beans with name "farmer": Caused by: org.jboss.weld.DeploymentException: An unresolvable ambiguous EL name exists for farmer; found [org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-LazyFarmer, org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-Farmer] at org.jboss.weld.Validator.validateBeanNames(Validator.java:321) at org.jboss.weld.Validator.validateDeployment(Validator.java:273) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:389) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:166) So I tried to step into weld RI code to see why this happened. This is what I found so far: 1. The Farmer class has a @Named annotation, and AbstractBean.initName() would set its name as the default name (the simple name of the class): "farmer". 2. The LazyFarmer class extends from Farmer class and does not have a @Named annotation, so AbstractBean.initName() does not assign any name to it. Its name is later assigned in AbstractBean.postSpecialize using its specialized bean's name (this.name = getSpecializedBean().getName()). Its specialized bean is its super class Farmer, and Farmer's name is "farmer". So now LazyFarmer's name is also "farmer". Seems from the RI code, it's expected these two beans will have the same name "farmer". So not sure how this test would pass with the current TCK/RI. This is also the cause of the deployment failure for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (WELD-249) Review and update Getting Started Developing Weld wiki page

by Pete Muir (JIRA)

Review and update Getting Started Developing Weld wiki page ----------------------------------------------------------- Key: WELD-249 URL: https://jira.jboss.org/jira/browse/WELD-249 Project: Weld Issue Type: Feature Request Components: Documentation Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.0.GA -- 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, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (CDITCK-102) org.jboss.jsr299.tck.tests.context.dependent.TransactionalInterceptor has incorrect postconstructor interceptor definition

by Marius Bogoevici (JIRA)

org.jboss.jsr299.tck.tests.context.dependent.TransactionalInterceptor has incorrect postconstructor interceptor definition -------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-102 URL: https://jira.jboss.org/jira/browse/CDITCK-102 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.CR1 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.0.1.GA, 1.1.0.CR1 According to the EJB Interceptor 1.1 specification, lifecycle interceptor methods defined on an interceptor class must have the signature: void <METHOD>(InvocationContext) -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-367) Alternative in bean XML does not restrict injection in CDIRunner

by Johan Eltes (JIRA)

Alternative in bean XML does not restrict injection in CDIRunner ---------------------------------------------------------------- Key: WELD-367 URL: https://jira.jboss.org/jira/browse/WELD-367 Project: Weld Issue Type: Bug Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Johan Eltes CDI runner (r5394) (SE engine?) resolves Alternatives even though they are not listed in beans.xml, leading to ambiguous dependencies. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-409) Remove custom equality for AnnotatedType and rely on cache/object equality

by Pete Muir (JIRA)

Remove custom equality for AnnotatedType and rely on cache/object equality -------------------------------------------------------------------------- Key: WELD-409 URL: https://jira.jboss.org/jira/browse/WELD-409 Project: Weld Issue Type: Bug Components: Reflection layer Reporter: Pete Muir Assignee: Stuart Douglas Fix For: 1.0.1.CR1 Currently we use the underlying class to perform equality, this is wrong. -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (WELD-406) Adding Annotated Types through the SPI needs comprehensive tests

by Stuart Douglas (JIRA)

Adding Annotated Types through the SPI needs comprehensive tests ---------------------------------------------------------------- Key: WELD-406 URL: https://jira.jboss.org/jira/browse/WELD-406 Project: Weld Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas There have been quite a few bugs in weld with regard to adding types through the SPI. We need tests that cover at least the following: - Adding multiple beans of the same class with different qualifiers - Adding multiple beans of the same class with the same qualifiers (but different method/field level annotations) - Adding the same producer method/field multiple times with different annotations -- 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, 2 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010