January 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-206) Add test to verify visibly of beans registered explicitly through an extension in non-bean archives

by Dan Allen (JIRA)

Add test to verify visibly of beans registered explicitly through an extension in non-bean archives --------------------------------------------------------------------------------------------------- Key: CDITCK-206 URL: https://issues.jboss.org/browse/CDITCK-206 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Dan Allen Add a test that answers this question: Can an extension register a bean programmatically for a class that resides in another non-bean archive? This question requires a short example which is available in the OpenTCK test suite and may be ported to the CDI TCK [1]. Assume one archive, a.jar, has the following contents: org/opentck/javaee/cdi/spi/beforebeandiscovery/BeanClassToRegister.class A second archive, b.jar, has the following contents: org/opentck/javaee/cdi/spi/beforebeandiscovery/AnotherBeanClassToRegister.class org/opentck/javaee/cdi/spi/beforebeandiscovery/AnotherManualBeanRegistrationExtension.class org/opentck/javaee/cdi/spi/beforebeandiscovery/ManualBeanRegistrationExtension.class META-INF/services/javax.enterprise.inject.spi.Extension AnotherBeanClassToRegister has an injection point of type BeanClassToRegister: public class AnotherBeanClassToRegister { @Inject private BeanClassToRegister collaborator; } BeanClassToRegister and AnotherBeanClassToRegister are added as beans programmatically in respective extensions listed in the service provider descriptor: public class ManualBeanRegistrationExtension implements Extension { public void registerBeans(@Observes BeforeBeanDiscovery event, BeanManager bm) { event.addAnnotatedType(bm.createAnnotatedType(BeanClassToRegister.class)); } } public class AnotherManualBeanRegistrationExtension implements Extension { public void registerBeans(@Observes BeforeBeanDiscovery event, BeanManager bm) { event.addAnnotatedType(bm.createAnnotatedType(AnotherBeanClassToRegister.class)); } } The two libraries, a.jar and b.jar are bundled in a web archive, test.war WEB-INF/lib/a.jar WEB-INF/lib/b.jar WEB-INF/beans.xml Deploying this archive to the reference implementation fails with an error message that the injection point from above cannot be satisfied. There appears to be a visibility problem across bean archives in this case. Adding META-INF/beans.xml to a.jar and removing the ManualBeanRegistrationExtension from b.jar resolves the issue in the reference implementation. [1] https://github.com/opentck/javaee_cdi/tree/master/src/test/java/org/opent... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (CDITCK-175) Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated

by Marius Bogoevici (JIRA)

Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated -------------------------------------------------------------------------------------------------------------- Key: CDITCK-175 URL: https://jira.jboss.org/browse/CDITCK-175 Project: CDI TCK Issue Type: Bug Reporter: Marius Bogoevici The package contains a few tests that exercise deployment errors due to invalid intercepted class definitions. The tests must be separated (perhaps in individual packages) in order to make sure that the test cases run in isolation (since there are multiple sources of errors, the deployment will fail if at least one is satisfied, but we want to test all). -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-347) META-INF/beans.xml not sufficient to activate CDI in WAR

by Dan Allen (JIRA)

META-INF/beans.xml not sufficient to activate CDI in WAR -------------------------------------------------------- Key: WELD-347 URL: https://jira.jboss.org/jira/browse/WELD-347 Project: Weld Issue Type: Bug Components: GlassFish Integration Affects Versions: 1.0.0.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 1.0.1.CR1 In GlassFish V3, if a WAR is deployed containing WEB-INF/classes/META-INF/beans.xml, CDI does not get activated (no beans are detected). Activation only happens if the WAR contains WEB-INF/beans.xml. I'm not sure why GlassFish V3 is having a problem finding beans.xml in the META-INF directory of the WAR classpath. I can't tell if it is a problem in Weld or a problem in GlassFish V3 somewhere. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (CDITCK-176) Decorator Elements in beans.xml use <decorator> not <class>

by Pete Muir (JIRA)

Decorator Elements in beans.xml use <decorator> not <class> ----------------------------------------------------------- Key: CDITCK-176 URL: https://jira.jboss.org/browse/CDITCK-176 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 Affected tests: testPassivationCapableBeanWithNonPassivatingDecoratorBeanConstructorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor.DecoratorWithNonPassivatingBeanConstructorTest) testPassivationCapableBeanWithNonPassivatingInitializerInDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod.DecoratorWithNonPassivatingInitializerMethodTest) testPassivationCapableBeanWithNonPassivatingDecoratorInjectedFieldFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField.DecoratorWithNonPassivatingInjectedFieldTest) testEnterpriseBeanWithNonPassivatingDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator.EnterpriseBeanWithNonPassivatingDecoratorTest) testDecoratorListedTwiceInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml.DecoratorListedTwiceInBeansXmlTest) testNonExistantDecoratorClassInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.nonExistantClassInBeansXml.NonExistantDecoratorClassInBeansXmlTest) -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-707) Intercepted bean method notifyAll() cannot be declared final

by Adam Warski (JIRA)

Intercepted bean method notifyAll() cannot be declared final ------------------------------------------------------------ Key: WELD-707 URL: https://jira.jboss.org/browse/WELD-707 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Adam Warski This started showing up after upgrading from M4 to M5, so to Weld 1.1.0. I'm using weldx, and as per the conversation on IRC with Pete this may be the cause. Exact message: WELD-001504 Intercepted bean method [method] public final native pl.softwaremill.service.organization.OrganizationService.notifyAll() (intercepted by pl.softwaremill.cdiext.transaction.TransactionalInterceptor) cannot be declared final -- 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, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (WELD-744) Interceptor and Decorator validation assumes that producer fields and methods will be public

by Pete Muir (JIRA)

Interceptor and Decorator validation assumes that producer fields and methods will be public -------------------------------------------------------------------------------------------- Key: WELD-744 URL: https://jira.jboss.org/browse/WELD-744 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.CR1 Needs to iterate over the class hierarchy looking at declared methods -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-657) Align instructions for running examples with Jetty

by Jozef Hartinger (JIRA)

Align instructions for running examples with Jetty -------------------------------------------------- Key: WELD-657 URL: https://jira.jboss.org/browse/WELD-657 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.0.Beta2 The examples/jsf/numberguess/readme.txt file describes how to run the example on Jetty using Eclipse. The reference documentation provides instructions for running the example on Jetty both from command line and Eclipse. These two information sources should be merged to provide the same instructions (or reference the other source). -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (WELDX-88) StartMain should support shutdown

by Edvin Syse (JIRA)

StartMain should support shutdown --------------------------------- Key: WELDX-88 URL: https://jira.jboss.org/jira/browse/WELDX-88 Project: Weld Extensions Issue Type: Feature Request Components: Weld Extensions Affects Versions: Java SE 1.0.1 Environment: n/a Reporter: Edvin Syse Priority: Minor When starting a project with org.jboss.weld.environment.se.StartMain, one would assume that weld.shutdown() would be run upon jvm shutdown, but it is not. This could easily be fixed with a minor adjustment. Please see the attached StartMain.java. -- 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
8
0 / 0

[JBoss JIRA] Created: (WELD-407) Provide warnings if AnnotatedType is not sensible

by Pete Muir (JIRA)

Provide warnings if AnnotatedType is not sensible ------------------------------------------------- Key: WELD-407 URL: https://jira.jboss.org/jira/browse/WELD-407 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 For example, if there are no constructors specified at all, or if the javaMember doesn't belong to the actual class hierarchy of the annotatedType -- 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
7
0 / 0

[JBoss JIRA] Created: (WELD-388) Fluent messages

by Nicklas Karlsson (JIRA)

Fluent messages --------------- Key: WELD-388 URL: https://jira.jboss.org/jira/browse/WELD-388 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Priority: Minor Make error messages read more fluent instead of the "Message : detail" format sometimes seen -- 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
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2011