November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-192) All test wars are invalid javaee artifacts since they have "Class-Path: null" manifest header

by David Jencks (JIRA)

All test wars are invalid javaee artifacts since they have "Class-Path: null" manifest header --------------------------------------------------------------------------------------------- Key: CDITCK-192 URL: https://jira.jboss.org/browse/CDITCK-192 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: David Jencks cf javaee_platform-6_0-fr-spec.pdf EE.8.2.1: Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension. Top level JAR files that are processed by a deployment tool should not contain Class-Path entries; such entries would, by definition, reference other files external to the deployment unit. A deployment tool is not required to process such external references. 2 So there should be no Class-Path header, and if there is it should only have .jar files in it. -- 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, 11 months

2
4
0 / 0

[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, 11 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, 11 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, 11 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (CDITCK-195) ExplicitConstructorSessionBean must have a no-arg constructor

by Marius Bogoevici (JIRA)

ExplicitConstructorSessionBean must have a no-arg constructor ------------------------------------------------------------- Key: CDITCK-195 URL: https://jira.jboss.org/browse/CDITCK-195 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: Marius Bogoevici Fix For: 1.0.3.CR4 ExplicitConstructorSessionBean from org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest must have a no-arg constructor. While the intent of the test is to exercise the usage of the @Inject-annotated constructor, a session bean class must also have a no-arg constructor, as required by EJB 3.1 spec 4.9.2. This may also be a disconnect between the EJB 3.1 and CDI spec, since the no-arg constructor may not actually be used, however it is still a requirement of the specification. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-180) org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public

by Lance Andersen (JIRA)

org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-180 URL: https://jira.jboss.org/browse/CDITCK-180 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.Final Reporter: Lance Andersen The following two classes are missing public in there declarations: org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard Specification version & section: The EJB Spec states the following in section "4.9.2 Session Bean Class": The class must be defined as public, must not be final, and must not be abstract. The class must be a top level class. This clearly violates that rule. These classes are not public. Tests Affected: testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean testSpecializingBeanHasNameOfSpecializedBean from org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest Output: [9/7/10 14:57:34:309 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract [9/7/10 14:57:34:312 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-137) org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest ------------------------------------------------------------------------------------------------------- Key: CDITCK-137 URL: https://jira.jboss.org/jira/browse/CDITCK-137 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Method : testChainedDecoratorInvocation In this test, TCK tests the injection points of the Decortor delegate. But it seems that this test is specific to Weld. In our case, we manage decorator stack via single delegate not via injection each decorator reference to DecoratorInvocationTest -- 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, 11 months

3
22
0 / 0

[JBoss JIRA] Created: (CDITCK-185) Session bean extending session bean

by Lance Andersen (JIRA)

Session bean extending session bean ----------------------------------- Key: CDITCK-185 URL: https://jira.jboss.org/browse/CDITCK-185 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.CR1 Reporter: Lance Andersen The EJB 3.0 Spec states the following in section "4.6.2 Session Bean Class": "The session bean class may have superclasses and/or superinterfaces. ...... A session bean class must not have a superclass that is itself a session bean class." Problem Description: According to the ejb-jar.xml, this is an ejb 3.0 ejb-jar: <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0"> </ejb-jar> So, we have an EJB 3.0 application. Yet, we see declared: @Stateful public class Farmer implements FarmerLocal { and @Stateful public class LazyFarmer extends Farmer implements LazyFarmerLocal, FarmerLocal { Farmer being extended by LazyFarmer violates the spec mentioned above. I believe this is allowed in the 3.1 spec, but not the 3.0 Spec. Tests Affected: testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean testSpecializingBeanHasNameOfSpecializedBean -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (CDITCK-182) Challenging the expected behaviour of SessionBeanPolicyTest in a hierarchical deployment

by Marius Bogoevici (JIRA)

Challenging the expected behaviour of SessionBeanPolicyTest in a hierarchical deployment ---------------------------------------------------------------------------------------- Key: CDITCK-182 URL: https://jira.jboss.org/browse/CDITCK-182 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.2.CR2 Reporter: Marius Bogoevici Fix For: 1.0.2.CR3 Test in cause: org.jboss.jsr299.tck.tests.policy.enterprise.SessionBeanPolicyTest The expectation is that EnabledEjb will be enabled, since it is enabled as an alternative in jar's beans.xml. However, the resolution in the test is done based on the BeanManager settings of the WAR that runs the test (in which said bean is not enabled as an alternative). -- 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, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010