December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-189) org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest persistence.xml Location Bug

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest persistence.xml Location Bug ----------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-189 URL: https://jira.jboss.org/browse/CDITCK-189 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest.war contains persistence.xml file in "WEB-INF/" location. According to the JPA specification, persistence unit root is "WEB-INF/classes" directory. Therefore persistence.xml file must be put into the "WEB-INF/classes/META-INF/persistence.xml". Because of above observation, test (testBeanTypesAndBindingTypesOfPersistenceContext) has failed. If we change the location of persistence.xml file, test has passed! Exclude list must be updated for including "testBeanTypesAndBindingTypesOfPersistenceContext" method. -- 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

13 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-187) org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest Bug

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest Bug --------------------------------------------------------------------------------- Key: CDITCK-187 URL: https://jira.jboss.org/browse/CDITCK-187 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest --> ServletTestRunner servlet mapping is not correct Must be mapped as "/*", but it is mapped as "/" - <servlet-mapping> - - <servlet-name>JBoss Test Harness Test Runner</servlet-name> - - <url-pattern>/</url-pattern> - </servlet-mapping> Therefore tests are getting 404 from server. -- 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

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (CDITCK-194) NewSimpleBeanTest and QualifierDefinitionTest expects @New beans to be enabled that should not be

by Stuart Douglas (JIRA)

NewSimpleBeanTest and QualifierDefinitionTest expects @New beans to be enabled that should not be ------------------------------------------------------------------------------------------------- Key: CDITCK-194 URL: https://jira.jboss.org/browse/CDITCK-194 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Stuart Douglas According to the spec an @New bean: "is enabled, in the sense of Section 5.1.2, "Enabled and disabled beans", if and only if some other enabled bean has an injection point with the qualifier @New(X.class) where X is the bean class." However org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest expects these @New beans to be enabled that are not injected anywhere. The tests that are in error are: testNewQualifierAndAnyBindingMutualExclusive(org.jboss.jsr299.tck.tests.definition.qualifier.QualifierDefinitionTest) testForEachSimpleBeanANewBeanExists(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasNoBeanELName(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasNoDisposerMethods(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasNoProducerFields(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasNoProducerMethods(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasNoStereotypes(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasOnlyNewBinding(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasSameConstructor(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasSameInitializers(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanHasSameInjectedFields(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) testNewBeanIsDependentScoped(org.jboss.jsr299.tck.tests.implementation.simple.newSimpleBean.NewSimpleBeanTest) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-196) DecoratorDefinitionTest FooBar does not extend Boo contrary to section 8.1.3

by David Jencks (JIRA)

DecoratorDefinitionTest FooBar does not extend Boo contrary to section 8.1.3 ---------------------------------------------------------------------------- Key: CDITCK-196 URL: https://jira.jboss.org/browse/CDITCK-196 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: David Jencks Section 8.1.3 says ... The delegate type of a decorator must implement or extend every decorated type (with exactly the same type parameters). However FooBar does not extend Boo. If the container checks the 8.1.3 rule the war for this test will not deploy. Changing FooBar to extend Boo satisfies the check. package directory is org/jboss/jsr299/tck/tests/decorators/definition/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (CDITCK-198) Non-contextual WebService injection test fails when deploying on JBoss AS 6.0 CR1 in TCK 1.1

by Marius Bogoevici (JIRA)

Non-contextual WebService injection test fails when deploying on JBoss AS 6.0 CR1 in TCK 1.1 --------------------------------------------------------------------------------------------- Key: CDITCK-198 URL: https://jira.jboss.org/browse/CDITCK-198 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Priority: Blocker Fix For: 1.1.0.CR1 https://jira.jboss.org/browse/CDITCK-197 for CDITCK 1.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on WELD-31: ------------------------------- It is. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Martin Gencur commented on WELD-31: ----------------------------------- Pete, do you think the current weld/master is compatible with Glassfish 3.1? I mean. I'm curious if I can run the test right now after updating GF with weld-trunk > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Sahoo Sahoo (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Sahoo Sahoo commented on WELD-31: --------------------------------- Unfortunately, we still maintain mojority of our developer tests/unit tests in that v2 directory. So, that's indeed the right URL. I don't see that changing anytime soon. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Martin Gencur commented on WELD-31: ----------------------------------- Sahoo , isn't the document (https://svn.java.net/svn/glassfish~svn/trunk/v2/appserv-tests/devtests/cd... ) dedicated for Glassfish v2? isn't there a newer one for GF 3? And also the sources of tests in the svn? > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Sahoo Sahoo (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Sahoo Sahoo commented on WELD-31: --------------------------------- You should be updating GF with Weld trunk build as long as Weld team thinks the weld changes are backward compatible. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010