January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Closed: (CDITCK-4) Add tests for metadata overriding including EJBs

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-4?page=com.atlassian.jira.plugi... ] Pete Muir closed CDITCK-4. -------------------------- > Add tests for metadata overriding including EJBs > ------------------------------------------------ > > Key: CDITCK-4 > URL: https://jira.jboss.org/jira/browse/CDITCK-4 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Jozef Hartinger > Fix For: 1.0.0.CR7 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-85) The CDI TCK assumes ear support by all impls

by Kyle Grucci (JIRA)

The CDI TCK assumes ear support by all impls -------------------------------------------- Key: CDITCK-85 URL: https://jira.jboss.org/jira/browse/CDITCK-85 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.CR1 Environment: All Reporter: Kyle Grucci The Web Profile spec falls under the Java EE 6 JSR which just went final. Since CDI is a requirement of the EE Web Profile, the CDI TCK must be able to run against it (ie it can't assume full EE and thus ear support). This is currently not the case since the TCK contains some ear files and some tests which rely upon them. At the very least it probably makes sense to have a second testsuite XML file which doesn't assume full EE. Otherwise impls of CDI which are not Full EE impls cannot run and pass the CDI TCK since the current testsuite xml file contains some ears. Until you are able to provide the alternate xml file, would it be possible for you to provide use with the tests to exclude whan not running on Full EE - (i.e. the tests which use ear files)? Thanks. -- 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, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (WELD-391) org.jboss.jsr299.tck.tests.decorators.invocation.EJBDecoratorInvocationTest.testEJBDecoratorInvocation()

by Pete Muir (JIRA)

org.jboss.jsr299.tck.tests.decorators.invocation.EJBDecoratorInvocationTest.testEJBDecoratorInvocation() -------------------------------------------------------------------------------------------------------- Key: WELD-391 URL: https://jira.jboss.org/jira/browse/WELD-391 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Reporter: Pete Muir Fix For: 1.0.1.CR1 Test is failing in trunk -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-394) org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest.testDependentScopedDecoratorsAreDependentObjectsOfBean()

by Pete Muir (JIRA)

org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest.testDependentScopedDecoratorsAreDependentObjectsOfBean() -------------------------------------------------------------------------------------------------------------------------- Key: WELD-394 URL: https://jira.jboss.org/jira/browse/WELD-394 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Reporter: Pete Muir Fix For: 1.0.1.CR1 Test is failing in trunk -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-395) org.jboss.jsr299.tck.tests.decorators.definition.DecoratorDefinitionTest.testDecoratorIsManagedBean()

by Pete Muir (JIRA)

org.jboss.jsr299.tck.tests.decorators.definition.DecoratorDefinitionTest.testDecoratorIsManagedBean() ----------------------------------------------------------------------------------------------------- Key: WELD-395 URL: https://jira.jboss.org/jira/browse/WELD-395 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Reporter: Pete Muir Fix For: 1.0.1.CR1 Test is failing in trunk -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-338) weld-numberguess example doesn't work with jboss-6.0.0.M1 in cluster

by Martin Gencur (JIRA)

weld-numberguess example doesn't work with jboss-6.0.0.M1 in cluster -------------------------------------------------------------------- Key: WELD-338 URL: https://jira.jboss.org/jira/browse/WELD-338 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.GA Reporter: Martin Gencur Fix For: 1.0.1.CR1 Trying to continue with the same session id on different jboss instance and web browser leads to the following exception on the instance's console: 12:41:21,767 WARN [SessionBasedJBossCacheService] Problem accessing session data : class java.lang.NullPointerException null Steps to reproduce: 1) download jboss-6.0.0.M1 (for example from http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....) 2) unzip it twice to different folders 3) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default 4) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 5) edit examples/jsf/numberguess/src/main/webapp-jboss5/WEB-INF/web.xml (add <distributable/> as its first tag so that the application..... !!! I don't know for sure if it is enough, maybe this is the problem !!!) 6) run mvn package in examples/jsf/numberguess 7) copy resulting war file (weld-numberguess.war) from numberguess/target/ directory to serve/all/farm directory at first jbossAS instance 8) remove cookies for "localhost" domain from web browser, disable cookies 9) go to http://localhost:8080/weld-numberguess/home.jsf, play for 2-3 times with application (try to guess a number) 10) copy&paste the url (for example "http://localhost:8080/weld-numberguess/home.jsf;jsessionid=VBobYX3Itd9fUI...") into another window with cookies disabled, change port number from 8080 to 8180 and go to the page 11) now you can see the exception in the second jboss instance's console and the application behaves like it doesn't know this session and starts from scratch -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Closed: (WELDINT-7) JBoss EJB 3.0 needs to delegate instance creation to Web Beans

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-7?page=com.atlassian.jira.plug... ] Pete Muir closed WELDINT-7. --------------------------- Fix Version/s: (was: 5.2.0.Beta6) Resolution: Duplicate Issue Assignee: Pete Muir > JBoss EJB 3.0 needs to delegate instance creation to Web Beans > -------------------------------------------------------------- > > Key: WELDINT-7 > URL: https://jira.jboss.org/jira/browse/WELDINT-7 > Project: Weld Integration > Issue Type: Feature Request > Components: JBoss EJB 3.0 integration > Reporter: Pete Muir > Assignee: Pete Muir > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELDINT-1) Implement module structure for JBoss AS

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-1?page=com.atlassian.jira.plug... ] Pete Muir commented on WELDINT-1: --------------------------------- See org.jboss.jsr299.tck.tests.deployment.packaging.bundledLibrary.LibraryInEarTest > Implement module structure for JBoss AS > --------------------------------------- > > Key: WELDINT-1 > URL: https://jira.jboss.org/jira/browse/WELDINT-1 > Project: Weld Integration > Issue Type: Feature Request > Components: Deployer > Reporter: Pete Muir > Assignee: Ales Justin > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > We need to provide the deployment structure to WB using BeanDeploymentArchive structure > http://anonsvn.jboss.org/repos/webbeans/ri/trunk/spi/src/main/java/org/jb... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-91) SimpleBeanLifecycleTest # testSpecializedBeanExtendsManagedBean Error

by Gurkan Erdogdu (JIRA)

SimpleBeanLifecycleTest # testSpecializedBeanExtendsManagedBean Error --------------------------------------------------------------------- Key: CDITCK-91 URL: https://jira.jboss.org/jira/browse/CDITCK-91 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Hi; In test SimpleBeanLifecycleTest # testSpecializedBeanExtendsManagedBean, MountainLion specializes the Lion so the managed bean with Lion is never resolved. So getBeans(Lion.class, TAME_LITERAL) returns bean with MountationLion not bean with Lion. Therefore assert bean != null; in the test case seems not to be 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-89) TCK on Policy Tests

by Gurkan Erdogdu (JIRA)

TCK on Policy Tests ------------------- Key: CDITCK-89 URL: https://jira.jboss.org/jira/browse/CDITCK-89 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Hi; I am currently testing org.jboss.jsr299.tck.tests.policy.PolicyAvailabilityTest. My questions are on the following test methods - testProducerPoliciesOnClass Sheep is produced by "EnabledSheepProducer" class that is defined in beans.xml and "NotEnabledSheepProducer" class that is not defined in beans.xml. So the first assertion in the test is correct 1) assert getBeans(Sheep.class, new AnnotationLiteral<Wild>(){}).size() == 2; But how the second assertion is correct? 2) assert getBeans(Sheep.class, new AnnotationLiteral<Tame>(){}).size() == 2; NotEnabledSheepProducer is not defined in beans.xml. So producer field and method that is contained in this class are disabled. - testProducerPoliciesOnMethodAndField CatProducer class defines producer field and method that are annotated with @Alternative. According to the spec section 5.1.1 "the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed in beans.xml". CatProducer class is not defined in beans.xml so those producer beans must be disabled and must not be used in resolutions. So the following assertions must be false, because CatProducer class is not defined in beans.xml assert getBeans(Cat.class, new AnnotationLiteral<Wild>(){}).size() == 2; assert getBeans(Cat.class, new AnnotationLiteral<Tame>(){}).size() == 2; -- 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, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010