March 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-458) Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error

by Ondrej Skutka (JIRA)

Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error ------------------------------------------------------------------------------------------------------------- Key: WELD-458 URL: https://jira.jboss.org/jira/browse/WELD-458 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: An interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as @Target(TYPE). If an interceptor for lifecycle callbacks declares an interceptor binding type that is defined @Target({TYPE, METHOD}), the con- tainer automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.interceptorForLifecycleTargetMethod.InterceptorForLifecycleTargetMethodTest In the TCK 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

12 years, 4 months

6
14
0 / 0

[JBoss JIRA] Created: (WELD-769) Intercepting a method in a bean where another method is final causes a VerifyError

by Adam Warski (JIRA)

Intercepting a method in a bean where another method is final causes a VerifyError ---------------------------------------------------------------------------------- Key: WELD-769 URL: https://jira.jboss.org/browse/WELD-769 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Beta2 Reporter: Adam Warski Used to work fine until AS6 CR1 (tested in M2 and M4). Stack trace: org.jboss.arquillian.impl.event.FiredEventException: java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:97) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeMethod(Invoker.java:494) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) Caused by: java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:103) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:52) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:42) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:32) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 27 more Caused by: org.jboss.weld.exceptions.DeploymentException: by java.lang.VerifyError: class pl.softwaremill.weldbugs.bug2.org$jboss$weld$bean-1ed4ae51-6ceb-40b2-899a-ed6d1f90409e$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug2$TestBean2_$$_WeldProxy overrides final method someMethod.()V at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:569) at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.produce(ManagedBean.java:250) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:332) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:59) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:669) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:743) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:137) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:869) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:881) at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:122) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:54) at org.jboss.weld.manager.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:116) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:113) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:93) ... 31 more Caused by: org.jboss.weld.exceptions.WeldException: by java.lang.VerifyError: class pl.softwaremill.weldbugs.bug2.org$jboss$weld$bean-1ed4ae51-6ceb-40b2-899a-ed6d1f90409e$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug2$TestBean2_$$_WeldProxy overrides final method someMethod.()V at org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:268) at org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:198) at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:564) ... 44 more Caused by: javassist.CannotCompileException: by java.lang.VerifyError: class pl.softwaremill.weldbugs.bug2.org$jboss$weld$bean-1ed4ae51-6ceb-40b2-899a-ed6d1f90409e$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug2$TestBean2_$$_WeldProxy overrides final method someMethod.()V at org.jboss.weld.util.bytecode.ClassFileUtils.toClass(ClassFileUtils.java:117) at org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:376) at org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:264) ... 46 more Caused by: java.lang.VerifyError: class pl.softwaremill.weldbugs.bug2.org$jboss$weld$bean-1ed4ae51-6ceb-40b2-899a-ed6d1f90409e$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug2$TestBean2_$$_WeldProxy overrides final method someMethod.()V at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.lang.ClassLoader.defineClass(ClassLoader.java:466) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.weld.util.bytecode.ClassFileUtils.toClass2(ClassFileUtils.java:143) at org.jboss.weld.util.bytecode.ClassFileUtils.toClass(ClassFileUtils.java:109) ... 48 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
11
0 / 0

[JBoss JIRA] Created: (WELD-510) Support for Portlet 2.0

by Neil Griffin (JIRA)

Support for Portlet 2.0 ----------------------- Key: WELD-510 URL: https://jira.jboss.org/jira/browse/WELD-510 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.1.Final Reporter: Neil Griffin There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue. Original Post: http://www.portletfaces.org/community/forums/-/message_boards/message/430... Here is a simple stacktrace of the problem: Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119) at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener The code for the bridge API is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... The code for the bridge IMPL is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... And the code for a sample portlet is here: http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-... -- 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

12 years, 7 months

12
36
0 / 0

[JBoss JIRA] Created: (CDITCK-204) TCK Harness property configuration broken

by Sivakumar Thyagarajan (JIRA)

TCK Harness property configuration broken ----------------------------------------- Key: CDITCK-204 URL: https://issues.jboss.org/browse/CDITCK-204 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sivakumar Thyagarajan As per http://docs.jboss.org/cdi/tck/reference/latest/en-US/html/test-harness-co..., a custom ConfigurationBuilder or an implementation of the SPI class such as org.jboss.jsr299.tck.spi.Beans could be provided by the TCK executor through a system property specifying the FQCN of the implementation class. However while trying to plug in a custom Beans SPI implementation or a ConfigurationBuilder using the system property, the default PropertiesBasedConfigurationBuilder seems to collate [1] all the properties file in the classpath and include the default implementations (bundled in the porting package or harness) as well. > [testng] Exception in thread "main" java.lang.IllegalArgumentException: More than one implementation of Beans specified by org.jboss.jsr299.tck.spi.Beans, not sure which one to use! > [testng] at org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:159) > [testng] at org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169) > [testng] at org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62) This prevents configuration of the TCK to use a custom SPI class implementation and/or ConfigurationBuilder. The only workaround seems to be providing a modified version of the existing porting package class and ensuring that it is loaded ahead. [1] [1] http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-51) Support EEJB environment in harness

by Pete Muir (JIRA)

Support EEJB environment in harness ----------------------------------- Key: CDITCK-51 URL: https://jira.jboss.org/jira/browse/CDITCK-51 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Affects Versions: 1.0.0.GA Reporter: Pete Muir Fix For: 1.1.0.CR1 -- 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

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-42) Investigate using dependency:copy-dependencies rather than dependency:copy as it looks in the reactor

by Pete Muir (JIRA)

Investigate using dependency:copy-dependencies rather than dependency:copy as it looks in the reactor ----------------------------------------------------------------------------------------------------- Key: CDITCK-42 URL: https://jira.jboss.org/jira/browse/CDITCK-42 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.0.CR3 -- 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

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-845) Do not bundle slf4j static logger binding in weld-servlet.jar

by Kariem Hussein (JIRA)

Do not bundle slf4j static logger binding in weld-servlet.jar ------------------------------------------------------------- Key: WELD-845 URL: https://issues.jboss.org/browse/WELD-845 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.1.0.Final Reporter: Kariem Hussein Bundling a static logger implementation with the weld-servlet.jar generates a warning that would not be necessary. The weld-servlet.jar (_uber jar_) is still (or arguably more) useful without the binding. Opened this ticket as [requested by Pete|http://seamframework.org/Community/Slf4jBindingInWeldservletjar#comm...] in response to a forum thread. This could be done similar to WELDSE-12 (requested in [this comment|https://issues.jboss.org/browse/WELDSE-12?focusedCommentId=125079...]). Assumed that WELDX and it successor SOLDER are not the right projects for this request. Related forum posts: * [slf4j Binding in weld-servlet.jar|http://seamframework.org/Community/Slf4jBindingInWeldser...] * [slf4j StaticLoggerBinder - This code should have never made it into the jar|http://seamframework.org/Community/Slf4jStaticLoggerBinderThisCodeSho...] * [Weld SE and slf4j|http://seamframework.org/Community/WeldSEAndSlf4j] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-760) Duplicate interceptor: More than one jar

by Robson Saraiva Ximenes (JIRA)

Duplicate interceptor: More than one jar ---------------------------------------- Key: WELD-760 URL: https://jira.jboss.org/browse/WELD-760 Project: Weld Issue Type: Bug Components: Weld SPI Affects Versions: 1.0.1.Final Environment: Just Weld 1.0.1.Final Reporter: Robson Saraiva Ximenes Assignee: Marius Bogoevici I'm getting the following error when I try to use my Interceptor: Duplicate interceptor class definition... The entire description for this issue was related here: http://seamframework.org/Community/AnotherInterceptorProblem -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
10
0 / 0

[JBoss JIRA] Created: (WELD-537) More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable.

by Nicklas Karlsson (JIRA)

More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable. --------------------------------------------------------------------------------------------------- Key: WELD-537 URL: https://jira.jboss.org/browse/WELD-537 Project: Weld Issue Type: Feature Request Components: Class Beans (Managed and Session) Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson The error message should be more detailed, currently ManagedBean.initializeAfterBeanDiscovery can have multiple conditions that set the passivationCapableBean to false (non-serializable interceptors etc) but it's hard to tell exactly what is wrong. -- 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

12 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (WELD-580) Around-Invoke Interceptors with wrong signature should cause DefinitionException

by Aslak Knutsen (JIRA)

Around-Invoke Interceptors with wrong signature should cause DefinitionException -------------------------------------------------------------------------------- Key: WELD-580 URL: https://jira.jboss.org/browse/WELD-580 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Aslak Knutsen Around-invoke methods have the following signature: Object <METHOD>(InvocationContext) throws Exception Interceptors that does not follow that should cause a DefinitionException. In current impl they are registered, enabled but can not be resolved on Bean lookup. -- 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

12 years, 9 months

7
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2011