September 2011 - weld-issues - Jboss List Archives

[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

12 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-971) Clean up weld poms

by Stuart Douglas (JIRA)

Clean up weld poms ------------------ Key: WELD-971 URL: https://issues.jboss.org/browse/WELD-971 Project: Weld Issue Type: Task Affects Versions: 1.1.2.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (CDITCK-224) Missing injection points for CircularDependencyTest

by Alexey Kazakov (JIRA)

Missing injection points for CircularDependencyTest --------------------------------------------------- Key: CDITCK-224 URL: https://issues.jboss.org/browse/CDITCK-224 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Alexey Kazakov It looks like that some beans tested by CircularDependencyTest miss injection points. See org.jboss.jsr299.tck.tests.lookup.circular.NormalSelfConsumingNormalProducer, org.jboss.jsr299.tck.tests.lookup.circular.DependentSelfConsumingNormalProducer, org.jboss.jsr299.tck.tests.lookup.circular.NormalSelfConsumingDependentProducer For instance there is a field *@SelfConsumingNormal1 Violation violation* in DependentSelfConsumingNormalProducer: {code} class DependentSelfConsumingNormalProducer { @SelfConsumingNormal1 Violation violation; @Produces @ApplicationScoped @SelfConsumingNormal1 public Violation produceViolation() { return new Violation(); } public void ping() { } } {code} which should be declared as an injection point: *@Inject* @SelfConsumingNormal1 Violation violation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
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

12 years, 7 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

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-970) Validator should not stop on first exception, but should continue to validate all beans

by Stuart Douglas (JIRA)

Validator should not stop on first exception, but should continue to validate all beans --------------------------------------------------------------------------------------- Key: WELD-970 URL: https://issues.jboss.org/browse/WELD-970 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.2.0.Beta1 It would be better if Validator displayed all the deployments problems in one go, rather than requiring a build deploy cycle for each problem -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-961) Use of request scoped component in a MDB results in a ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped

by Stefano Travelli (JIRA)

Use of request scoped component in a MDB results in a ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: WELD-961 URL: https://issues.jboss.org/browse/WELD-961 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.1.Final Environment: Glassfish 3.1 or JBoss AS 6 Reporter: Stefano Travelli Injecting a request scoped component in a Message Driven Bean results in the following exception when a message is received: ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped The CDI specification states that "the request scope is active ... during any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-969) org.jboss.jsr299.tck.tests.context.ContextTest is failing

by Stuart Douglas (JIRA)

org.jboss.jsr299.tck.tests.context.ContextTest is failing --------------------------------------------------------- Key: WELD-969 URL: https://issues.jboss.org/browse/WELD-969 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.2.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-968) Weld does not interceptor timeout methods without an @Timeout annotation

by Stuart Douglas (JIRA)

Weld does not interceptor timeout methods without an @Timeout annotation ------------------------------------------------------------------------ Key: WELD-968 URL: https://issues.jboss.org/browse/WELD-968 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.2.0.Beta1 There are many other ways of defining a timeout method: @Schedule TimedObject Deployment Descriptor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues September 2011