January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Closed: (WELD-83) Fix activities tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-83?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-83. ------------------------- Resolution: Done Assignee: Pete Muir All tests that have ever passed for activities, do so again :-) > Fix activities tests > -------------------- > > Key: WELD-83 > URL: https://jira.jboss.org/jira/browse/WELD-83 > Project: Weld > Issue Type: Task > Components: Activities > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.0.1.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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELDINT-32) Injectiing TimerService or Session context fails

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-32?page=com.atlassian.jira.plu... ] Pete Muir commented on WELDINT-32: ---------------------------------- A couple of problems here: 1) Weld-jboss-int is not properly detecting the no-interface view EJB as an EJB, but instead as a managed bean. We are waiting on confirmation of no-interface view support in trunk before fixing this 2) Weld is using the wrong prefix for the TimerService lookup (and probably others too) https://jira.jboss.org/jira/browse/WELD-385 > Injectiing TimerService or Session context fails > ------------------------------------------------ > > Key: WELDINT-32 > URL: https://jira.jboss.org/jira/browse/WELDINT-32 > Project: Weld Integration > Issue Type: Bug > Components: JBoss EJB 3.0 integration > Environment: Windows Vista x86_64, JDK1.6.0_17 > Reporter: Nikolay Elenkov > Assignee: Pete Muir > > Injection using @Resource fails with this exception: > java.lang.RuntimeException: Error resolving property asyncTest against base null > org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:120) > org.jboss.weld.integration.webtier.jsf.ForwardingELResolver.getValue(ForwardingELResolver.java:51) > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) > com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > ... > caused by > java.lang.RuntimeException: Error looking up java:/comp/env/weldtest.weldjsf.AsyncTest/timerService in JNDI > org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:38) > org.jboss.weld.util.Beans.injectEEFields(Beans.java:692) > org.jboss.weld.bean.ManagedBean$1$1.proceed(ManagedBean.java:218) > org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:51) > Code: > @Stateless > public class AsyncTest { > @Resource > private TimerService timerService; > @Resource > private SessionContext sessionContext > According to Nicklas Karlsson this is a 'bug in the integration where JBoss reports to Weld on which EJB:s are available where' (see forum link) > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-383) JNDI prefix is wrong

by Koichi Kobayashi (JIRA)

JNDI prefix is wrong -------------------- Key: WELD-383 URL: https://jira.jboss.org/jira/browse/WELD-383 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.0.GA Reporter: Koichi Kobayashi In org.jboss.weld.injection.spi.helpers.AbstractResourceServices private static final String RESOURCE_LOOKUP_PREFIX = "java:/comp/env"; The right prefix is "java:comp/env".(delete a slash before "comp") -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-307) Weld needs to treat a passivating pseudo-scope as a definition error as part of beforeBeanDiscovery.addScope()

by Pete Muir (JIRA)

Weld needs to treat a passivating pseudo-scope as a definition error as part of beforeBeanDiscovery.addScope() -------------------------------------------------------------------------------------------------------------- Key: WELD-307 URL: https://jira.jboss.org/jira/browse/WELD-307 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir Fix For: 1.0.1.CR1 *.deployment.lifecycle.broken.passivatingScope.AddingPassivatingScopeTest.testAddingScope -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Closed: (WELD-76) OOME on servlet container redeployment

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-76?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-76. ------------------------- Resolution: Done Assignee: Pete Muir (was: Shane Bryzak) Recent fixes to memory usage appear to have resolved this, I was able to complete 10 redeployments with the standard amount of memory > OOME on servlet container redeployment > -------------------------------------- > > Key: WELD-76 > URL: https://jira.jboss.org/jira/browse/WELD-76 > Project: Weld > Issue Type: Bug > Reporter: Christian Bauer > Assignee: Pete Muir > Priority: Critical > Fix For: 1.0.1.CR1 > > > Redeploying /examples/wicket/numberguess (no code changes, just repeated deploy/undeploy cycles) to Jetty, running from within IntelliJ but in a separate VM. > With default max heap size (JConsole reports 84 MB) after 3 redeployment cycles or with Xmx256m after about 10 cycles, the VM simply hangs at 100% CPU load with a full heap and the log: > [Timer-1] 07:57:54,804 DEBUG [org.jboss.webbeans.bootstrap.AbstractBeanDeployer] Bean: Built-in implicit javax.inject.Instance bean > [Timer-1] 07:57:54,805 DEBUG [org.jboss.webbeans.bootstrap.AbstractBeanDeployer] Bean: org.jboss.webbeans.bean-web-module-NewManagedBean-org.jboss.webbeans.wicket.BeanManagerLookup > [Timer-1] 07:57:54,806 DEBUG [org.jboss.webbeans.bootstrap.AbstractBeanDeployer] Bean: org.jboss.webbeans.bean-web-module-NewManagedBean-org.jboss.webbeans.conversation.NumericConversationIdGenerator > [Timer-1] 07:57:55,879 DEBUG [org.jboss.webbeans.bootstrap.AbstractBeanDeployer] Bean: org.jboss.webbeans.bean-web-module-NewManagedBean-org.teleal.hub.bookmarks.ui.HelloWorld > [Timer-1] 07:57:55,881 DEBUG [org.jboss.webbeans.bootstrap.WebBeansBootstrap] Web Beans initialized. Validating beans. > (Had to stop the process with KILL signal.) > Sometimes it doesn't hang and I get this instead: > java.lang.OutOfMemoryError: Java heap space > at java.util.jar.Attributes.read(Attributes.java:377) > at java.util.jar.Manifest.read(Manifest.java:182) > at java.util.jar.Manifest.<init>(Manifest.java:52) > at java.util.jar.JarFile.getManifestFromReference(JarFile.java:165) > at java.util.jar.JarFile.getManifest(JarFile.java:146) > at sun.misc.URLClassPath$JarLoader$2.getManifest(URLClassPath.java:693) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:221) > at java.net.URLClassLoader.access$000(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:392) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374) > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2291) > at java.lang.Class.getDeclaredFields(Class.java:1743) > at org.jboss.webbeans.introspector.jlr.WBClassImpl.<init>(WBClassImpl.java:210) > at org.jboss.webbeans.introspector.jlr.WBClassImpl.of(WBClassImpl.java:130) > at org.jboss.webbeans.resources.ClassTransformer$1.call(ClassTransformer.java:59) > at org.jboss.webbeans.resources.ClassTransformer$1.call(ClassTransformer.java:55) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.jboss.webbeans.util.collections.ConcurrentCache.putIfAbsent(ConcurrentCache.java:125) > at org.jboss.webbeans.resources.ClassTransformer.loadClass(ClassTransformer.java:54) > at org.jboss.webbeans.introspector.jlr.WBClassImpl.<init>(WBClassImpl.java:146) > at org.jboss.webbeans.introspector.jlr.WBClassImpl.of(WBClassImpl.java:130) > at org.jboss.webbeans.resources.ClassTransformer$1.call(ClassTransformer.java:59) > at org.jboss.webbeans.resources.ClassTransformer$1.call(ClassTransformer.java:55) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.jboss.webbeans.util.collections.ConcurrentCache.putIfAbsent(ConcurrentCache.java:125) > With Xmx1024m, after about 20 cycles: > java.lang.OutOfMemoryError: PermGen space > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:675) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$000(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:392) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374) > at org.apache.wicket.settings.Settings.<init>(Settings.java:139) > at org.apache.wicket.Application.getSettings(Application.java:874) > at org.apache.wicket.Application.getPageSettings(Application.java:545) > at org.apache.wicket.Application.internalInit(Application.java:972) > at org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplication.java:551) > at org.jboss.webbeans.wicket.WebBeansApplication.internalInit(WebBeansApplication.java:71) > at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:693) > at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:658) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) > at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250) > at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) > at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.deployer.ContextDeployer.deploy(ContextDeployer.java:268) > at org.mortbay.jetty.deployer.ContextDeployer.redeploy(ContextDeployer.java:287) > at org.mortbay.jetty.deployer.ContextDeployer.access$100(ContextDeployer.java:67) > at org.mortbay.jetty.deployer.ContextDeployer$ScannerListener.fileChanged(ContextDeployer.java:99) > at org.mortbay.util.Scanner.reportChange(Scanner.java:464) > at org.mortbay.util.Scanner.reportDifferences(Scanner.java:330) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-53) Remove library version definitions from build.properties

by Jozef Hartinger (JIRA)

Remove library version definitions from build.properties -------------------------------------------------------- Key: CDITCK-53 URL: https://jira.jboss.org/jira/browse/CDITCK-53 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Reporter: Jozef Hartinger Priority: Minor Fix For: 1.0.1.CR1 Library version definitions like weld-deployer.version=5.2.0-SNAPSHOT weld.version=1.0.0-SNAPSHOT are present in the jsr299-tck-1.0.0/weld/jboss-as/build.properties although they are not used and confusing. -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Assigned: (WELD-8) Reduce reliance on invokeOnInstance by mapping against interfaces at deploy

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-8?page=com.atlassian.jira.plugin.... ] Pete Muir reassigned WELD-8: ---------------------------- Assignee: (was: Pete Muir) > Reduce reliance on invokeOnInstance by mapping against interfaces at deploy > --------------------------------------------------------------------------- > > Key: WELD-8 > URL: https://jira.jboss.org/jira/browse/WELD-8 > Project: Weld > Issue Type: Feature Request > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Fix For: 1.0.1.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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-369) DependentContextTest shows a ThreadLocal not being cleaned up properly

by Pete Muir (JIRA)

DependentContextTest shows a ThreadLocal not being cleaned up properly ---------------------------------------------------------------------- Key: WELD-369 URL: https://jira.jboss.org/jira/browse/WELD-369 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Reporter: Pete Muir Priority: Minor Fix For: 1.0.1.CR1 The currentInjectionPoint in BeanManager isn't being cleared properly, instead it has a FieldInjectionPoint, probably created by applyDecorators() 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Updated: (WELD-63) Create proper servlet lifecycle tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-63?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-63: -------------------------- Fix Version/s: 1.0.2.CR1 (was: 1.0.1.CR1) > Create proper servlet lifecycle tests > ------------------------------------- > > Key: WELD-63 > URL: https://jira.jboss.org/jira/browse/WELD-63 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Priority: Minor > Fix For: 1.0.2.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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-73) Seam2 integration 1.0.0.BETA1

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-73?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-73. ------------------------- Fix Version/s: (was: 1.0.1.CR1) Resolution: Out of Date Will be done in Seam. > Seam2 integration 1.0.0.BETA1 > ----------------------------- > > Key: WELD-73 > URL: https://jira.jboss.org/jira/browse/WELD-73 > Project: Weld > Issue Type: Component Upgrade > Reporter: Pete Muir > Assignee: Pete Muir > -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010