April 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDINT-50) Create 6.0.0.Alpha8 release for weld-int

by John Bailey (JIRA)

Create 6.0.0.Alpha8 release for weld-int ---------------------------------------- Key: WELDINT-50 URL: https://jira.jboss.org/jira/browse/WELDINT-50 Project: Weld Integration Issue Type: Release Affects Versions: 6.0.0.Beta8 Reporter: John Bailey Assignee: John Bailey Fix For: 6.0.0.Beta7 Create the release 6.0.0.Alpha8 for weld-int -- 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, 10 months

2
4
0 / 0

[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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDINT-23) ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean

by Jozef Hartinger (JIRA)

ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean ------------------------------------------------------------------------------------------------------ Key: WELDINT-23 URL: https://jira.jboss.org/jira/browse/WELDINT-23 Project: Weld Integration Issue Type: Bug Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 5.2.0.Beta5 org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForFilter() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForJsfManagedBean() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForTagLibraryListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForServletListener() -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDINT-53) Singleton beans not recognized

by Nicklas Karlsson (JIRA)

Singleton beans not recognized ------------------------------ Key: WELDINT-53 URL: https://jira.jboss.org/jira/browse/WELDINT-53 Project: Weld Integration Issue Type: Bug Components: Weld Bootstrapper Reporter: Nicklas Karlsson org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testSingleton* tests fail because the JbossSessionBean31DescriptorAdaptor gives singleton=false for @Singleton beans -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDINT-57) Make addition in WeldDiscoveryEnvironment public

by Ales Justin (JIRA)

Make addition in WeldDiscoveryEnvironment public ------------------------------------------------ Key: WELDINT-57 URL: https://jira.jboss.org/jira/browse/WELDINT-57 Project: Weld Integration Issue Type: Task Components: Weld Bootstrapper Reporter: Ales Justin Assignee: Ales Justin Fix For: 6.0.0.CR1 -- 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, 10 months

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

13 years, 10 months

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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-142) Bug in DependentContextTest

by Gurkan Erdogdu (JIRA)

Bug in DependentContextTest --------------------------- Key: CDITCK-142 URL: https://jira.jboss.org/jira/browse/CDITCK-142 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu public void testDependentsDestroyedWhenProducerMethodCompletes(), this tests tests destroying of dependents when producer methods completes. But specification does not talk about it. AFAIK, producer methods are also beans and their dependents are destroyed when bean is destroyed or CreationalContext # release is called. But test destroys producer bean dependents when method completes. I think this is not correct. -- 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, 10 months

4
6
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

13 years, 10 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

13 years, 10 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2010