November 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Work started: (WELDX-5) Spring integration

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-5?page=com.atlassian.jira.plugin... ] Work on WELDX-5 started by Marius Bogoevici. > Spring integration > ------------------ > > Key: WELDX-5 > URL: https://jira.jboss.org/jira/browse/WELDX-5 > Project: Weld Extensions > Issue Type: Feature Request > Components: Spring integration > Reporter: Gavin King > Assignee: Marius Bogoevici > Priority: Minor > Fix For: Spring integration 1.0.0.BETA1 > > -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-289) Missing elements in the beans.xsd

by Jason Porter (JIRA)

Missing elements in the beans.xsd ---------------------------------- Key: WELD-289 URL: https://jira.jboss.org/jira/browse/WELD-289 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Jason Porter Attachments: missing_xsd_elements.patch The xsd is missing definitions for <alternatives> and <stereotype>. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-301) ProducerMethod.checkProducerMethod only checked method declarations in direct implemented interface and not super interfaces

by Hong Zhang (JIRA)

ProducerMethod.checkProducerMethod only checked method declarations in direct implemented interface and not super interfaces ---------------------------------------------------------------------------------------------------------------------------- Key: WELD-301 URL: https://jira.jboss.org/jira/browse/WELD-301 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Environment: X86/Ubuntu Reporter: Hong Zhang Priority: Critical I am investigating the deployment failure when running org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefinitionTest. The deployment failed due to some validation failure in weld RI code. It complains that produceLightYellowPear method of LightYellowPearTree is not declared in LightYellowPearTree business interface. But LightYellowTree implements LightYellowPearTreeLocal which extends from PearTreeLocal which delares the produceLightYellowPear method. This seems a weld RI bug to me after stepping into the RI code: In ProducerMethod.checkProducerMethod, when it's a session bean, it will check for its implemented interface and super class for whether they declared this business method. But the problem is it only goes to its direct implemented interface and not the interface hierarchy. In this case it's true that the LightYellowPearTreeLocal does not declare this method, but PearTreeLocal which the LightYellowPearTreeLocal extends from does declare this method. The RI code should be modified to check for the whole interface hierarchy and not just the direct implemented interface. -- 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

16 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (WELD-308) Event errors not checked

by Santiago Pericas-Geertsen (JIRA)

Event errors not checked ------------------------ Key: WELD-308 URL: https://jira.jboss.org/jira/browse/WELD-308 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.0.0.GA Environment: Solaris x86 / JDK 6u16 / GF v3 Reporter: Santiago Pericas-Geertsen The following TCK test, *.deployment.lifecycle.broken.addDefinitionError.AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError fails because no exception is reported when app is deployed. There is an extension class, BeanDiscoveryObserver, which calls, event.addDefinitionError(new AssertionError(...)) in a method that observes the AfterBeanDiscovery event. The spec says that if such an error is reported, the deployment should fail, so the tests appears to be correct. I cannot find any code in Weld that would check the list of errors in an instance of AfterBeanDiscoveryImpl, though. This suggests that an error check is missing in Weld. The method WeldBootstrap.deployBeans() calls, AfterBeanDiscoveryImp.fire(...) which is a static method that creates a new instance of AfterBeanDiscoveryImpl. However, that instance is discarded after its fire() method is called. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-65) The sig test jar(s) should be in the 299 TCK bundle

by Kyle Grucci (JIRA)

The sig test jar(s) should be in the 299 TCK bundle --------------------------------------------------- Key: CDITCK-65 URL: https://jira.jboss.org/jira/browse/CDITCK-65 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.CR1 Environment: All Reporter: Kyle Grucci I did not see the sig tests tool jars in the TCK bundle - only a reference of where to get them on java.net. The jars required to run the test in the TCK should be in the TCK bundle. This makes things much easier on the users. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-302) ProcessInjectionTarget<X> doesn't work for servlets, filters

by Jitendra Kotamraju (JIRA)

ProcessInjectionTarget<X> doesn't work for servlets, filters ------------------------------------------------------------ Key: WELD-302 URL: https://jira.jboss.org/jira/browse/WELD-302 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.0.0.GA Environment: GlassFish v3 Reporter: Jitendra Kotamraju weld RI calls for (RIBean<?> bean : beans) { ... else if (bean instanceof AbstractClassBean<?>) { ProcessBeanInjectionTarget.fire(manager, (AbstractClassBean<?>) bean); But beans is not populated for Servlet and someother EE components that support injection. Hence ProcessInjectionTarget<TestServlet> is not received by an observer. -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Closed: (WELD-11) Support setter injection

by Gavin King (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-11?page=com.atlassian.jira.plugin... ] Gavin King closed WELD-11. -------------------------- Resolution: Out of Date CDI supports setter injection: @Inject setFoo(Foo foo) { .... } > Support setter injection > ------------------------ > > Key: WELD-11 > URL: https://jira.jboss.org/jira/browse/WELD-11 > Project: Weld > Issue Type: Feature Request > Components: Class Beans (Managed and Session) > Reporter: Kabir Khan > Fix For: 1.0.1.CR1 > > > On 15 Aug 2009, at 10:17, Pete Muir wrote: > It's pretty straightforward, probably 2h work, inc. a few tests. > Essentially, we just have to add some MethodInjectionPoints when the class based beans are created, and call them when a bean is injected. The only hard part is deciding on the exact semantics - like do the method names have to be JavaBean compliant (always start isXXX) and have void return type? what are the error conditions (can't put @Produces, @Disposes, @Observes on them) etc. > Put a feature request in JIRA for CR2 I guess (until CR1 I have to concentrate on spec features really). > On 14 Aug 2009, at 18:12, Kabir Khan wrote: > kkhan:pmuir: How much work would it be to support setter injection > [17:58]kkhan:? > [17:59]kkhan:I know you said it is not required for 1.0 of CDI, but I think it would be nice to have > [17:59]kkhan:especially from the MC side -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-66) Sig test command to test all 299 required packages should be in the bundle

by Kyle Grucci (JIRA)

Sig test command to test all 299 required packages should be in the bundle -------------------------------------------------------------------------- Key: CDITCK-66 URL: https://jira.jboss.org/jira/browse/CDITCK-66 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Environment: All. Reporter: Kyle Grucci I can't find the command to run the sig tests for checking all packages required by 299. The readme in the bundle gives an example, but it seems to just test the decorator package. The command to run the sig tests for all required 299 packages should be in the TCK. Otherwise you place the onus on the user to construct the packages to test... which is more error prone and can/will lead to some packages not being tested. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-297) A weld-jsf.jar should be created to cleanly and clearly separate the part of Weld that is JSF dependant

by Francisco Jose Peredo Noguez (JIRA)

A weld-jsf.jar should be created to cleanly and clearly separate the part of Weld that is JSF dependant ------------------------------------------------------------------------------------------------------- Key: WELD-297 URL: https://jira.jboss.org/jira/browse/WELD-297 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.0.GA Reporter: Francisco Jose Peredo Noguez While it would have been great to have Weld proportionate everything Seam proportionates, I think, a very clear line should be painted to prevent bloating. I think Weld should get thinner, and its boundaries clearly defined, therfore I think a weld-jsf.jar should be created (the JSF equivalent of weld-wicket.jar) to cleanly and clearly separate the part of Weld that is JSF dependant (and the part that is not) -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-294) @Logger sample in Chapter 19 is incorrect

by Francisco Jose Peredo Noguez (JIRA)

@Logger sample in Chapter 19 is incorrect ----------------------------------------- Key: WELD-294 URL: https://jira.jboss.org/jira/browse/WELD-294 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.GA Reporter: Francisco Jose Peredo Noguez In the Weld 1.0.0 documentation at 19.1. Weld Logger I can read this example: import org.jboss.weld.annotation.Logger; import org.jboss.weld.log.Log; public class Checkout { private @Inject @Logger Log log; public void invoiceItems() { ShoppingCart cart; ... log.debug("Items invoiced for {0}", cart); } } But there is no org.jboss.weld.log.Log class in Weld -- 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

16 years, 4 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009