August 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, 4 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, 4 months

2
3
0 / 0

[JBoss JIRA] Closed: (WELDINT-2) Problems using WebBeans in multiple Applications (EARS)

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELDINT-2?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed WELDINT-2. --------------------------- Fix Version/s: (was: 6.0.0.CR1) Resolution: Out of Date No updates > Problems using WebBeans in multiple Applications (EARS) > ------------------------------------------------------- > > Key: WELDINT-2 > URL: https://jira.jboss.org/browse/WELDINT-2 > Project: Weld Integration > Issue Type: Bug > Components: Weld Bootstrapper > Environment: JBoss 5.0.1.GA, > TEsted with WebBean 1.0.0.Preview and today snapshot > Reporter: Martin Eigenbrodt > Assignee: Ales Justin > Priority: Critical > Attachments: bug.zip > > > Multiple EARS that use webbeans seem to interfer. > I've prepared a simple testcase. The zip contains an ear "earA.ear" that includes a war with a simple jsf page and a backing bean. > The backing beans has got a method that is used within the jsf page: > > public String getText() { > return "Hello World!"; > } > The second ear "empty.ear" does only contain an empty beans.xml in the META-INF dir. > If you deploy just earA.ear you can view the jsf page at http://localhost:8080/EarAWar/index.jsf . It display a Heading "Test" and the line "Hello World" below. > If you now deploy the earA.ear and the empty.ear and restart, the "Hello World" will be gone. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-166) Test should be on 1.0.1 exclude list: org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod

by Kyle Grucci (JIRA)

Test should be on 1.0.1 exclude list: org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-166 URL: https://jira.jboss.org/browse/CDITCK-166 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.Final Environment: All Reporter: Kyle Grucci Priority: Minor Fix For: 1.0.1.Final The following test needs to be added to the 1.0.1 TCK exclude list... org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod I just ran the 1.0.1 Final 299 TCK (with the latest exclude list that you have posted) with the following results... 827 Passed 1 Failed The 1 failure is from this test... org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod >From earlier emails, it appears that this test should be on the 1.0.1 exclude list per issue # CDITCK-157. -- 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

14 years, 4 months

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

14 years, 4 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

14 years, 4 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, 4 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, 4 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-143) Bug in SimpleLifecycleTest

by Gurkan Erdogdu (JIRA)

Bug in SimpleLifecycleTest -------------------------- Key: CDITCK-143 URL: https://jira.jboss.org/jira/browse/CDITCK-143 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu MEthods : testBeanCreateInjectsDependenciesAndInvokesInitializerToInstantiateInstance testCreateReturnsSameBeanPushed Those methods test CreationalContext#push. But implementation does not require to support push method according to specification. -- 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, 4 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010