March 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDINT-55) BeanManager should be available in JNDI under java:comp/BeanManager

by Marius Bogoevici (JIRA)

BeanManager should be available in JNDI under java:comp/BeanManager ------------------------------------------------------------------- Key: WELDINT-55 URL: https://jira.jboss.org/jira/browse/WELDINT-55 Project: Weld Integration Issue Type: Bug Components: Weld Bootstrapper Affects Versions: 6.0.0.Beta9 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Priority: Critical Currently using java:app/BeanManager and breaki -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDINT-48) Merge VFS3 changes

by John Bailey (JIRA)

Merge VFS3 changes ------------------ Key: WELDINT-48 URL: https://jira.jboss.org/jira/browse/WELDINT-48 Project: Weld Integration Issue Type: Task Affects Versions: 6.0.0.Beta7 Reporter: John Bailey Assignee: Pete Muir Fix For: 6.0.0.Beta8 Need to merge the changes from vfs3-int branch to 6.0.0.Beta7_VFS3_int branch -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-136) QualifierDefinitionTest.testDefaultQualifierForInjectionPoint() doesn't test qualifiers for Injection points.

by Alexey Kazakov (JIRA)

QualifierDefinitionTest.testDefaultQualifierForInjectionPoint() doesn't test qualifiers for Injection points. ------------------------------------------------------------------------------------------------------------- Key: CDITCK-136 URL: https://jira.jboss.org/jira/browse/CDITCK-136 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.Final Reporter: Alexey Kazakov There is assert injectionPoint.getBean().getQualifiers().contains(new DefaultLiteral()); in QualifierDefinitionTest.testDefaultQualifierForInjectionPoint() test. But shouldn't there be injectionPoint.getQualifiers() instead of injectionPoint.getBean().getQualifiers()? This method is supposted to test the default quailifier for an injection point, but not for a bean isn't it? -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-121) Bug in BeanManagerTest

by Gurkan Erdogdu (JIRA)

Bug in BeanManagerTest ---------------------- Key: CDITCK-121 URL: https://jira.jboss.org/jira/browse/CDITCK-121 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu public void testGetPassivationCapableBeanById() { Bean<?> bean = getCurrentManager().getBeans(Cow.class).iterator().next(); assert PassivationCapable.class.isAssignableFrom(bean.getClass()); ...... Bean SPI class does not extends PassivationCapable interface. Therefore, PassivationCapable.class.isAssignableFrom(bean.getClass()); must not be true. OWB beans do not implement PassivationCapable interface as a default. Therefore this is specific to 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

14 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-114) Implement test for assertion 6.7.4 tb using a filter to check for the exception

by Pete Muir (JIRA)

Implement test for assertion 6.7.4 tb using a filter to check for the exception ------------------------------------------------------------------------------- Key: CDITCK-114 URL: https://jira.jboss.org/jira/browse/CDITCK-114 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.1.0.CR1 It's very hard to test the exception from the client, as there is not even a requirement that the server send a particular error page. However a servlet, installed as the outer most filter, should be able to find the exception is thrown. I don't know how you check if a new transient conversation is created. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (CDITCK-109) Rewrite all conversation tests to be remote JSF tests

by Pete Muir (JIRA)

Rewrite all conversation tests to be remote JSF tests ----------------------------------------------------- Key: CDITCK-109 URL: https://jira.jboss.org/jira/browse/CDITCK-109 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.1.GA, 1.1.0.CR1 This is needed because the conversation context is not actually active in other requests, and also Conversation is not available -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-116) Typo in dd-override-report

by Jozef Hartinger (JIRA)

Typo in dd-override-report -------------------------- Key: CDITCK-116 URL: https://jira.jboss.org/jira/browse/CDITCK-116 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.GA Reporter: Jozef Hartinger Priority: Trivial The document says "Deployment Descripters overriden by the TCK" while it should say "Deployment Descriptors overriden by the TCK" -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-134) Injection point not on a passivation capable bean

by Pete Muir (JIRA)

Injection point not on a passivation capable bean ------------------------------------------------- Key: CDITCK-134 URL: https://jira.jboss.org/jira/browse/CDITCK-134 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Gurkan Erdogdu Fix For: 1.0.2.CR1 org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField These packages tests decorator injection points to check if they are passivation capable dependency or not, however the injection point is not on a passivation capable bean -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (CDITCK-120) Seems a bug in DependentContextTest

by Gurkan Erdogdu (JIRA)

Seems a bug in DependentContextTest ----------------------------------- Key: CDITCK-120 URL: https://jira.jboss.org/jira/browse/CDITCK-120 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest belows test methods directly use Bean#create method to create actual bean instances. But this method must not be used directly, instead of BeanManager#getReference must be used. Therefore tests are failed. Methods ----------------- testDependentScopedDecoratorsAreDependentObjectsOfBean testDependentScopedInterceptorsAreDependentObjectsOfBean -- 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, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (WELD-269) Registration of a custom implementation of the Decorator interface fails

by Jozef Hartinger (JIRA)

Registration of a custom implementation of the Decorator interface fails ------------------------------------------------------------------------ Key: WELD-269 URL: https://jira.jboss.org/jira/browse/WELD-269 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Assignee: Marius Bogoevici Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.decorators.custom.CustomDecoratorTest.testCustomImplementationOfDecoratorInterface() -- 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, 5 months

3
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2010