November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-178) DecoratorDefinitionTest.testDecoratedTypes() asserts that a superinterface of the decorator bean class is not a decorated type.

by Alexey Kazakov (JIRA)

DecoratorDefinitionTest.testDecoratedTypes() asserts that a superinterface of the decorator bean class is not a decorated type. ------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-178 URL: https://jira.jboss.org/browse/CDITCK-178 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Alexey Kazakov See public void testDecoratedTypes() { List<Decorator<?>> decorators = getCurrentManager().resolveDecorators(FooBar.TYPES); assert decorators.size() == 1; assert decorators.get(0).getDecoratedTypes().size() == 3; assert decorators.get(0).getDecoratedTypes().contains(Foo.class); assert decorators.get(0).getDecoratedTypes().contains(Bar.class); assert decorators.get(0).getDecoratedTypes().contains(Baz.class); assert !decorators.get(0).getDecoratedTypes().contains(Serializable.class); assert !decorators.get(0).getDecoratedTypes().contains(FooDecorator.class); assert !decorators.get(0).getDecoratedTypes().contains(AbstractFooDecorator.class); assert !decorators.get(0).getDecoratedTypes().contains(Boo.class); } But Boo is a superinterface of FooDecorator (not a superclass). And according of JSR-299 8.1 it's a decorated type: 8.1. Decorator beans A decorator is a managed bean. The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for java.io.Serializable. -- 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
8
0 / 0

[JBoss JIRA] Created: (CDITCK-183) DestroyedInstanceReturnedByGetTest seems broken

by Mark Struberg (JIRA)

DestroyedInstanceReturnedByGetTest seems broken ----------------------------------------------- Key: CDITCK-183 URL: https://jira.jboss.org/browse/CDITCK-183 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Mark Struberg DestroyedInstanceReturnedByGetTest currently calls {noformat} destroyContext(getCurrentManager().getContext(SessionScoped.class)); setContextActive(getCurrentManager().getContext(SessionScoped.class)); {noformat} The problem is that destroying the SessionContext will render it inactive. So the getContext() call in the following line will throw a ContextNotActiveException according to the spec 6.5.1: "If no active context object exists for the scope type, the container throws a ContextNotActiveException." -- 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-177) EnterpriseBeanNotDiscoveredAsManagedBeanTest is invalid

by Pete Muir (JIRA)

EnterpriseBeanNotDiscoveredAsManagedBeanTest is invalid ------------------------------------------------------- Key: CDITCK-177 URL: https://jira.jboss.org/browse/CDITCK-177 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3, 1.1.0.CR1 The spec only requires that "A top-level Java class is not a managed bean if it is annotated with any of the EJB component-defining annotations" It mentions nothing about implementing EnterpriseBean -- 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

1
2
0 / 0

[JBoss JIRA] Created: (CDITCK-184) session beans missing public

by Lance Andersen (JIRA)

session beans missing public ----------------------------- Key: CDITCK-184 URL: https://jira.jboss.org/browse/CDITCK-184 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.CR1 Reporter: Lance Andersen The following classes (Session beans) are missing public in their declarations, which causes 25 additional tests to fail (all in org.jboss.jsr299.tck.tests: context/passivating/broken/enterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptor/Espoo_Broken.java context/passivating/broken/enterpriseBeanWithNonPassivatingConstructorFieldInDecorator/Espoo_Broken.java context/passivating/broken/enterpriseBeanWithNonPassivatingInitializerInDecorator/Espoo_Broken.java context/passivating/broken/enterpriseBeanWithNonPassivatingInitializerParameterInInterceptor/Espoo_Broken.java context/passivating/broken/enterpriseBeanWithNonPassivatingInjectedFieldInDecorator/Espoo_Broken.java context/passivating/broken/enterpriseBeanWithNonSerializableIntializerMethod/Espoo_Broken.java context/passivating/broken/unserializableSimpleInjectedIntoPassivatingEnterpriseBean/Espoo_Broken.java context/passivating/Turku.java definition/qualifier/enterprise/EnglishBorderCollie.java definition/qualifier/enterprise/FamousCat.java definition/qualifier/enterprise/SkinnyHairlessCat.java definition/qualifier/enterprise/TameSkinnyHairlessCat.java event/broken/observer/notBusinessMethod/TibetanTerrier_Broken.java implementation/enterprise/broken/singletonWithRequestScope/Greyhound_Broken.java implementation/enterprise/broken/singletonWithSessionScope/IrishTerrier_Broken.java implementation/enterprise/broken/statelessWithApplicationScope/Dachshund_Broken.java implementation/enterprise/broken/statelessWithConversationScope/Boxer_Broken.java implementation/enterprise/broken/statelessWithRequestScope/Beagle_Broken.java implementation/enterprise/broken/statelessWithSessionScope/Bullmastiff_Broken.java implementation/enterprise/definition/Ape.java implementation/enterprise/definition/Giraffe.java implementation/enterprise/definition/Lion.java implementation/enterprise/definition/Monkey.java implementation/enterprise/definition/Pitbull.java implementation/enterprise/definition/PolarBear.java implementation/enterprise/newBean/GoldenRetriever.java implementation/enterprise/newBean/Lion.java implementation/enterprise/newBean/Order.java implementation/enterprise/newBean/WrappedEnterpriseBean.java inheritance/specialization/enterprise/broken/directlyExtendsSimpleBean/Tractor_Broken.java inheritance/specialization/simple/broken/extendejb/FarmEquipment.java policy/enterprise/EnabledEjb.java policy/enterprise/NotEnabledEjb.java Specification version & section: The EJB 3.1 Spec states the following in section "4.9.2 Session Bean Class" (and Ejb 3.0 Spec 4.6.2): 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 (25): testBeanTypesAreLocalInterfacesWithoutWildcardTypesOrTypeVariablesWithSuperInterfaces testBeanWithNonSerializableImplementationInjectedIntoTransientFieldOK testForEachEnterpriseBeanANewBeanExists testInjectionOfDependentPrimitiveProductIntoNormalBean testInjectionOfDependentSerializableProductIntoNormalBean testManagedBeanWithSerializableDecoratorOK testManagedBeanWithSerializableImplementationClassOK testManagedBeanWithSerializableInterceptorClassOK testNewBeanHasNoBeanELName testNewBeanHasNoObservers testNewBeanHasNoStereotypes testNewBeanIsDependentScoped testNewBeanIsHasOnlyNewBinding testNonSerializableProducerFieldDeclaredPassivatingThrowsIllegalProductException testPassivatingScopeProducerMethodReturnsUnserializableObjectNotOk testPassivationCapableProducerFieldIsOK testPassivationCapableProducerMethodIsOK testPassivationOccurs testRemoteInterfacesAreNotInAPITypes testSingletonWithRequestScopeFails testSingletonWithSessionScopeFails testSpecializingClassDirectlyExtendsEnterpriseBean testSpecializingClassDirectlyExtendsSimpleBean testStatelessWithRequestScopeFails testStatelessWithSessionScopeFails -- 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
11
0 / 0

[JBoss JIRA] Created: (CDITCK-181) Tests try to use beanManager.getContext() to get a scope they know is inactive

by Pete Muir (JIRA)

Tests try to use beanManager.getContext() to get a scope they know is inactive ------------------------------------------------------------------------------ Key: CDITCK-181 URL: https://jira.jboss.org/browse/CDITCK-181 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3 org.jboss.jsr299.tck.tests.lookup.clientProxy.ClientProxyTest.testInactiveScope() org.jboss.jsr299.tck.tests.event.EventTest.testStaticObserverMethodInvoked() -- 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

1
2
0 / 0

[JBoss JIRA] Created: (CDITCK-138) org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest ------------------------------------------------------------------- Key: CDITCK-138 URL: https://jira.jboss.org/jira/browse/CDITCK-138 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu In the testIsDelegateMethod(), assert cat.getInjectionPoint().isDelegate(); But Cat injection point is not decorator delegate point. -- 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
16
0 / 0

[JBoss JIRA] Created: (CDITCK-174) ProcessObserverMethod Type parameters are inverted

by Pete Muir (JIRA)

ProcessObserverMethod Type parameters are inverted -------------------------------------------------- Key: CDITCK-174 URL: https://jira.jboss.org/browse/CDITCK-174 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.2.CR3 All these tests suffer from inverted generic type parameters to ProcessObserverMethod testApplicationContextShared(org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest) testGetAnnotatedMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testGetObserverMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testProcessObserverMethodEventsSent(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testAddDefinitionError(org.jboss.jsr299.tck.tests.extensions.observer.broken.definitionError.ProcessObserverMethodErrorTest) testExceptionIsDefinitionError(org.jboss.jsr299.tck.tests.extensions.observer.broken.exception.ProcessObserverMethodExceptionTest) -- 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

1
3
0 / 0

[JBoss JIRA] Created: (WELD-735) Custom registered Contexts should be auto exposed as Beans

by Aslak Knutsen (JIRA)

Custom registered Contexts should be auto exposed as Beans ---------------------------------------------------------- Key: WELD-735 URL: https://jira.jboss.org/browse/WELD-735 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Affects Versions: 1.1.0.Beta1 Reporter: Aslak Knutsen Priority: Minor In Beta-1 all Built-In Contexts are now auto registered as Beans in Weld, Beans which you can Inject where you need to. But Custom registered contexts are not. It's normal to do the registration of a context and the activation of a context on two different locations in the code base, and being able to inject the context where the activation should accure sounds a lot nicer then some awkward static field or simmilar. -- 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
2
0 / 0

[JBoss JIRA] Created: (WELD-538) Unsatisfied dependency in interceptor still checked for serialization, resulting in NPE

by Nicklas Karlsson (JIRA)

Unsatisfied dependency in interceptor still checked for serialization, resulting in NPE --------------------------------------------------------------------------------------- Key: WELD-538 URL: https://jira.jboss.org/browse/WELD-538 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Given a serializable interceptor with a @Inject Logger log but no producer for it you get a java.lang.NullPointerException at org.jboss.weld.util.Beans.isPassivationCapableDependency(Beans.java:175) at org.jboss.weld.bootstrap.Validator.validateInjectionPointPassivationCapable(Validator.java:335) at org.jboss.weld.bootstrap.Validator.validateCdiBoundInterceptors(Validator.java:224) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:170) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:363) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:349) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:402) at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:121) [:6.0.0-SNAPSHOT] because it checks for passivation on a null-resolved bean -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-753) Trim/Normalize extra whitespace surrounding classnames in beans.xml deployment descriptor

by Sivakumar Thyagarajan (JIRA)

Trim/Normalize extra whitespace surrounding classnames in beans.xml deployment descriptor ----------------------------------------------------------------------------------------- Key: WELD-753 URL: https://jira.jboss.org/browse/WELD-753 Project: Weld Issue Type: Bug Components: Infrastructure Affects Versions: 1.1.0.Beta2 Reporter: Sivakumar Thyagarajan Priority: Minor Interceptors, Decorators and Alternatives could have class elements and a user may add additional whitespace while specifying the classname as shown below: <interceptors> <class> test.beans.TransactionInterceptor</class> </interceptors> Today the BeansXml parser implementation does not trim the extraneous whitespace around the classname as pass them as such ("\n test.beans.TransactionInterceptor" to the container's classloader(Thread context classloader) in DefaultResourceLoader. Since most classloaders' implementation of loadClass() doesn't trim the classnames, it results in a ClassNotFoundException. Caused by: java.lang.ClassNotFoundException: test.beans.TransactionInterceptor at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1518) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1368) at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:52) It would be nice if the class element is normalized and stripped of any extraneous whitespace before asking the TCL to load the class. -- 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, 12 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010