November 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Updated: (WELD-75) Standardize logging and exception messages

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-75?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-75: -------------------------- Fix Version/s: 1.0.0.GA (was: 1.0.0.CR2) > Standardize logging and exception messages > ------------------------------------------ > > Key: WELD-75 > URL: https://jira.jboss.org/jira/browse/WELD-75 > Project: Weld > Issue Type: Task > Components: Infrastructure > Reporter: Pete Muir > Priority: Blocker > Fix For: 1.0.0.GA > > -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-260) java.util.ConcurrentModificationException : WeldBootstrap.deployBeans

by Roger Kitain (JIRA)

java.util.ConcurrentModificationException : WeldBootstrap.deployBeans --------------------------------------------------------------------- Key: WELD-260 URL: https://jira.jboss.org/jira/browse/WELD-260 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Environment: mac glassfish Reporter: Roger Kitain Small app containing an extension (residing in gf/lib) and deployed war. when server starts up (or the app is being deployed): WARNING: Exception while dispatching an event java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$ValueIterator.next(HashMap.java:822) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:151) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:88) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:322) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:169) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:310) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:141) at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:573) at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:459) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:391) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:376) at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:195) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-258) Multiple Process* events reported if extension is in war on GlassFish

by Pete Muir (JIRA)

Multiple Process* events reported if extension is in war on GlassFish --------------------------------------------------------------------- Key: WELD-258 URL: https://jira.jboss.org/jira/browse/WELD-258 Project: Weld Issue Type: Bug Components: Events, GlassFish Integration, Infrastructure Environment: Weld 1.0.0 (SNAPSHOT), GlassFish Reporter: Paul Sandoz Priority: Critical Fix For: 1.0.0.CR2 If an Extention is defined in a jar located in WEB-INF/lib then that jar will receive ProcessInjectionTarget events but modification of the InjectionTarget, for example adapting the InjectionTarget does not have any effect. The methods on the adapted InjectionTarget instance are never invoked. I am using a build of Weld from the trunk that Roger Kitain gave me to test. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-247) Adaption of InjectionTarget does not take effect on a ProcessInjectionTarget event for an Extension in a jar of WEB-INF/lib

by Paul Sandoz (JIRA)

Adaption of InjectionTarget does not take effect on a ProcessInjectionTarget event for an Extension in a jar of WEB-INF/lib --------------------------------------------------------------------------------------------------------------------------- Key: WELD-247 URL: https://jira.jboss.org/jira/browse/WELD-247 Project: Weld Issue Type: Bug Components: Events, GlassFish Integration, Infrastructure Environment: Weld 1.0.0 (SNAPSHOT), GlassFish Reporter: Paul Sandoz Priority: Blocker If an Extention is defined in a jar located in WEB-INF/lib then that jar will receive ProcessInjectionTarget events but modification of the InjectionTarget, for example adapting the InjectionTarget does not have any effect. The methods on the adapted InjectionTarget instance are never invoked. I am using a build of Weld from the trunk that Roger Kitain gave me to test. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-243) Weld should not deliver startup events to non-extension beans

by Pete Muir (JIRA)

Weld should not deliver startup events to non-extension beans ------------------------------------------------------------- Key: WELD-243 URL: https://jira.jboss.org/jira/browse/WELD-243 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir Fix For: 1.0.0.CR2 -- 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

16 years, 5 months

1
4
0 / 0

[JBoss JIRA] Updated: (WELD-2) Custom bean implementation - methods not called by RI

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-2?page=com.atlassian.jira.plugin.... ] Pete Muir updated WELD-2: ------------------------- Fix Version/s: 1.0.1.CR1 (was: 1.0.0.CR2) > Custom bean implementation - methods not called by RI > ----------------------------------------------------- > > Key: WELD-2 > URL: https://jira.jboss.org/jira/browse/WELD-2 > Project: Weld > Issue Type: Bug > Components: Bootstrap and Metamodel API > Reporter: Jozef Hartinger > Fix For: 1.0.1.CR1 > > > getBeanClass(), getStereotypes(), isNullable() and isPolicy() are not called by the RI on a custom implementation of Bean interface > org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testGetStereotypesCalled() > org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testIsNullableCalled() -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-2) Custom bean implementation - methods not called by RI

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-2?page=com.atlassian.jira.plugin.... ] Pete Muir updated WELD-2: ------------------------- Description: getBeanClass(), getStereotypes(), isNullable() and isPolicy() are not called by the RI on a custom implementation of Bean interface org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testGetStereotypesCalled() org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testIsNullableCalled() was: getBeanClass(), getStereotypes(), isNullable() and isPolicy() are not called by the RI on a custom implementation of Bean interface org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testGetBeanClassCalled() org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testGetStereotypesCalled() org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testIsPolicyCalled() org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testIsNullableCalled() > Custom bean implementation - methods not called by RI > ----------------------------------------------------- > > Key: WELD-2 > URL: https://jira.jboss.org/jira/browse/WELD-2 > Project: Weld > Issue Type: Bug > Components: Bootstrap and Metamodel API > Reporter: Jozef Hartinger > Fix For: 1.0.0.CR2 > > > getBeanClass(), getStereotypes(), isNullable() and isPolicy() are not called by the RI on a custom implementation of Bean interface > org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testGetStereotypesCalled() > org.jboss.jsr299.tck.tests.definition.bean.custom.CustomBeanImplementationTest.testIsNullableCalled() -- 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

16 years, 5 months

1
0
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

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Updated: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-80?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-80: -------------------------- Component/s: Scopes & Contexts > Passivation of stateful session beans results in a loss of reference to injected object > --------------------------------------------------------------------------------------- > > Key: WELD-80 > URL: https://jira.jboss.org/jira/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 > Reporter: John Ament > Fix For: 1.0.1.CR1 > > Attachments: statefulpassivate.zip > > > See forum post -- 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

16 years, 5 months

1
0
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

16 years, 5 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009