October 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-219) Dependency injection does not work on a managed bean if it is intercepted

by Jozef Hartinger (JIRA)

Dependency injection does not work on a managed bean if it is intercepted ------------------------------------------------------------------------- Key: WELD-219 URL: https://jira.jboss.org/jira/browse/WELD-219 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.interceptors.definition.InterceptorDefinitionTest.testManagedBeanIsIntercepted() -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-227) InjectionPoint implementation not passivation capable

by Jozef Hartinger (JIRA)

InjectionPoint implementation not passivation capable ----------------------------------------------------- Key: WELD-227 URL: https://jira.jboss.org/jira/browse/WELD-227 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 FieldInjectionPoint and ParameterInjectionPoint are not serializable. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-233) A sub-set of events are reported to Extension classes defined in jar files that are in WEB-INF/lib

by Paul Sandoz (JIRA)

A sub-set of events are reported to Extension classes defined in jar files that are in WEB-INF/lib -------------------------------------------------------------------------------------------------- Key: WELD-233 URL: https://jira.jboss.org/jira/browse/WELD-233 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.CR1 Environment: GlassFish v3 and Weld 1.0.0-CR1-SP1 Reporter: Paul Sandoz Attachments: jcditest.zip Only the following events are reported: BEFORE BEAN DISCOVERY, PROCESS ANNOTATED TYPE, AFTER BEAN DISCOVERY and AFTER DEPLOYMENT VALIDATION -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-239) AbstractProducerBean.checkReturnValue seems to check against the wrong injection point

by Huy Le (JIRA)

AbstractProducerBean.checkReturnValue seems to check against the wrong injection point -------------------------------------------------------------------------------------- Key: WELD-239 URL: https://jira.jboss.org/jira/browse/WELD-239 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.0.CR1 Environment: Weld 1.0.0.CR1, embedded Jetty Reporter: Huy Le I was running a modified version of the numberguess example (attached to this issue) and got the following exception which doesn't seem quite right: javax.enterprise.inject.IllegalProductException: Producers cannot produce non-serializable instances for injection into non-transient fields of passivating beans Producer: org.jboss.weld.bean-web-module-ProducerMethod-org.jboss.weld.examples.numberguess.FacesContextManager.getFacesContext() Injection Point: field org.jboss.weld.examples.numberguess.Game.maxNumber at org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:201) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:287) at org.jboss.weld.context.AbstractMapContext.get(AbstractMapContext.java:104) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:139) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:97) at javax.faces.context.FacesContext_$$_javassist_7.getELContext(FacesContext_$$_javassist_7.java) at org.jboss.weld.examples.numberguess.Generator.getMaxNumber(Generator.java:38) 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.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:111) at org.jboss.weld.examples.numberguess.Generator_$$_javassist_6.getMaxNumber(Generator_$$_javassist_6.java) 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.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:227) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:148) at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:117) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:286) at org.jboss.weld.context.DependentContext.get(DependentContext.java:62) at org.jboss.weld.BeanManagerImpl.getReference(BeanManagerImpl.java:899) at org.jboss.weld.BeanManagerImpl.getReference(BeanManagerImpl.java:945) at org.jboss.weld.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:967) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:78) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:683) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:695) at org.jboss.weld.bean.ManagedBean$1$1.proceed(ManagedBean.java:195) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:51) at org.jboss.weld.bean.ManagedBean$1.inject(ManagedBean.java:189) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:115) at org.jboss.weld.context.AbstractMapContext.get(AbstractMapContext.java:104) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:139) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:97) at org.jboss.weld.examples.numberguess.Game_$$_javassist_5.getNumber(Game_$$_javassist_5.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Not sure if my analysis is correct, but it seems that: 1. FieldInjectionPoint for maxNumber is set as the current injection point in BeanManagerImpl 2. Producer method for maxNumber is invoked 3. The getELContext method is invoked on the FacesContext proxy 4. The getProxiedInstance method is invoked on ClientProxyMethodHandler which causes the producer method for FacesContext to be invoked 5. The checkReturnValue on AbstractProducerBean is invoked, but it is checking the FacesContext return value against the injection point for maxNumber (since this is still the current injection point) an an IllegalProductException is thrown since maxNumber must be serializable (but not FacesContext) -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-238) Classes specified in beans.xml/interceptors should not need to be annotated with @Interceptor

by Jozef Hartinger (JIRA)

Classes specified in beans.xml/interceptors should not need to be annotated with @Interceptor --------------------------------------------------------------------------------------------- Key: WELD-238 URL: https://jira.jboss.org/jira/browse/WELD-238 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Assignee: Marius Bogoevici Fix For: 1.0.0.CR2 Currently, the RI requires every class defined in beans.xml under "interceptors" element to be annotated with @Interceptor. Otherwise, the container throws the following exception : "org.jboss.jsr299.tck.DeploymentError: org.jboss.weld.DeploymentException: Class org.jboss.jsr299.tck.tests.interceptors.definition.custom.Interceptor1 is enabled as an interceptor, but it does not have the appropriate annotation" However, this is too restrictive (and conflicting with the spec), since in case when the interceptor is registered via portable extension (using custom implementation of the Interceptor interface), the class should not be required to be annotated with @Interceptor. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-237) permalink: maven-cli-plugin 0.6.3.CR3 is not on repo anymore. Should it be 0.7 instead?

by Steven Boscarine (JIRA)

permalink: maven-cli-plugin 0.6.3.CR3 is not on repo anymore. Should it be 0.7 instead? ----------------------------------------------------------------------------------------- Key: WELD-237 URL: https://jira.jboss.org/jira/browse/WELD-237 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.CR1 Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 09:04:01-0400) Java version: 1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.28-16-generic" arch: "amd64" Family: "unix" Reporter: Steven Boscarine Attachments: changeVersionOfCLI_Plugin_to_0_7.diff Permalink isn't building because it cannot find maven-cli-plugin 0.6.3.CR3. Upgrading to 0.7 seems to work. [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.twdata.maven -DartifactId=maven-cli-plugin -Dversion=0.6.3.CR3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.twdata.maven -DartifactId=maven-cli-plugin -Dversion=0.6.3.CR3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.twdata.maven:maven-cli-plugin:maven-plugin:0.6.3.CR3 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus repository (http://repository.codehaus.org/), twdata-m2-repository.googlecode.com (http://twdata-m2-repository.googlecode.com/svn) org.twdata.maven:maven-cli-plugin:maven-plugin:0.6.3.CR3 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus repository (http://repository.codehaus.org/), twdata-m2-repository.googlecode.com (http://twdata-m2-repository.googlecode.com/svn) -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-226) 'Default' event observer doesn't get notified when firing events (with qualifiers) directly with the manager

by Fabio Wang (JIRA)

'Default' event observer doesn't get notified when firing events (with qualifiers) directly with the manager ------------------------------------------------------------------------------------------------------------ Key: WELD-226 URL: https://jira.jboss.org/jira/browse/WELD-226 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.0.0.CR1 Environment: Apache Tomcat 6.0.20 Reporter: Fabio Wang An observer with this signature: observe(@Observes XEvent event) {...} is not notified when an event is fired like this: manager.fireEvent(new XEvent(), new AnyLiteralQualifier(), new AnyLiteralQualifier2(), ...); If the observer specifies any of the LiteralQualifiers (or any subset of them, except the empty one), then it's notified. However, if fired like this: manager.fireEvent(new XEvent(), new DefaultLiteral(), new AnyLiteralQualifier(), new AnyLiteralQualifier2(), ...); with the DefaultLiteral among the qualifiers, then it works as expected. Firing an event with an Event<XEvent> also works. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-221) Infinite Mutual Recursion in HierarchyDiscovery.resolveType

by Clint Popetz (JIRA)

Infinite Mutual Recursion in HierarchyDiscovery.resolveType ----------------------------------------------------------- Key: WELD-221 URL: https://jira.jboss.org/jira/browse/WELD-221 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.CR1 Reporter: Clint Popetz Assignee: Pete Muir The following: abstract class ChoiceParent<T> { } class Choice<T, E> extends ChoiceParent<T> { public Choice<T, E> aMethod() { return null; } } will produce an infinite recursion between resolveType and resolveTypeParameter if weld tries to load it. I've added a class to test/ in org.jboss.weld.test.unit.implementation.annotatedItem that triggers this, but it caused the build to fail, so it's been excluded. To enable, remove the @Classes annotation from the top of org.jboss.weld.test.unit.implementation.annotatedItem.ClassAnnotatedItemTest, which is excluding the deployment of Choice and ChoiceParent -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-228) Exception is not thrown when a non-contextual Java EE component defines an injection point of type InjectionPoint

by Jozef Hartinger (JIRA)

Exception is not thrown when a non-contextual Java EE component defines an injection point of type InjectionPoint ----------------------------------------------------------------------------------------------------------------- Key: WELD-228 URL: https://jira.jboss.org/jira/browse/WELD-228 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.lookup.injectionpoint.broken.not.bean.InjectionPointTest.testDefinitionErrorDetected() -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-236) Child BDA Not Processed

by Roger Kitain (JIRA)

Child BDA Not Processed ----------------------- Key: WELD-236 URL: https://jira.jboss.org/jira/browse/WELD-236 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Environment: MAC Reporter: Roger Kitain Assignee: Pete Muir Given the following Deployment structure: deployment bda (jar) bda (war) bda (jar) The war's child bda (jar) will never get processed. See WeldBootstrap.visit method (around line 135). -- 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, 5 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2009