February 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-440) Update JBoss AS version to 6 M2

by Pete Muir (JIRA)

Update JBoss AS version to 6 M2 ------------------------------- Key: WELD-440 URL: https://jira.jboss.org/jira/browse/WELD-440 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.1.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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (CDITCK-110) Account for NonexistentConversationException

by Pete Muir (JIRA)

Account for NonexistentConversationException -------------------------------------------- Key: CDITCK-110 URL: https://jira.jboss.org/jira/browse/CDITCK-110 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.1.GA, 1.1.0.CR1 org.jboss.jsr299.tck.tests.context.conversation.client.ClientConversationContextTest.testConversationPropagationToNonExistentConversationLeadsToTransientConversation() assumes that no exception is thrown. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (CDITCK-113) Classes are not public

by Pete Muir (JIRA)

Classes are not public ---------------------- Key: CDITCK-113 URL: https://jira.jboss.org/jira/browse/CDITCK-113 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.1.GA It's not reasonable to expect classloading to be able to access non-public classes: org.jboss.jsr299.tck.tests.context.passivating.NumberConsumer org.jboss.jsr299.tck.tests.context.passivating.SerializableCityConsumer org.jboss.jsr299.tck.tests.context.passivating.HelsinkiNonSerializable org.jboss.jsr299.tck.tests.context.passivating.Television -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDITCK-112) org.jboss.jsr299.tck.tests.implementation.enterprise.broken.singletonWithConversationScope.SingletonWithConversationScopeTest requires EJB 3.1 version in ejb-jar.xml

by Pete Muir (JIRA)

org.jboss.jsr299.tck.tests.implementation.enterprise.broken.singletonWithConversationScope.SingletonWithConversationScopeTest requires EJB 3.1 version in ejb-jar.xml --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-112 URL: https://jira.jboss.org/jira/browse/CDITCK-112 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.1.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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (CDITCK-67) test applications failed to deploy due to "unresolvable ambiguous EL name exists"

by Hong Zhang (JIRA)

test applications failed to deploy due to "unresolvable ambiguous EL name exists" --------------------------------------------------------------------------------- Key: CDITCK-67 URL: https://jira.jboss.org/jira/browse/CDITCK-67 Project: CDI TCK Issue Type: CTS Challenge Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Environment: Ubuntu/X86 Reporter: Hong Zhang Priority: Critical I am investigation the test failures for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest class. The deployment failed for the application due to some validation failure in weld RI code. >From the stack trace, it found two beans with name "farmer": Caused by: org.jboss.weld.DeploymentException: An unresolvable ambiguous EL name exists for farmer; found [org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-LazyFarmer, org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-Farmer] at org.jboss.weld.Validator.validateBeanNames(Validator.java:321) at org.jboss.weld.Validator.validateDeployment(Validator.java:273) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:389) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:166) So I tried to step into weld RI code to see why this happened. This is what I found so far: 1. The Farmer class has a @Named annotation, and AbstractBean.initName() would set its name as the default name (the simple name of the class): "farmer". 2. The LazyFarmer class extends from Farmer class and does not have a @Named annotation, so AbstractBean.initName() does not assign any name to it. Its name is later assigned in AbstractBean.postSpecialize using its specialized bean's name (this.name = getSpecializedBean().getName()). Its specialized bean is its super class Farmer, and Farmer's name is "farmer". So now LazyFarmer's name is also "farmer". Seems from the RI code, it's expected these two beans will have the same name "farmer". So not sure how this test would pass with the current TCK/RI. This is also the cause of the deployment failure for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest -- 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, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (WELD-442) Session event listener throws javax.ejb.NoSuchEJBException after certain time of inactivity in a session

by Martin Gencur (JIRA)

Session event listener throws javax.ejb.NoSuchEJBException after certain time of inactivity in a session -------------------------------------------------------------------------------------------------------- Key: WELD-442 URL: https://jira.jboss.org/jira/browse/WELD-442 Project: Weld Issue Type: Bug Reporter: Martin Gencur When using stateful session beans, the following exception is thrown after approximately 11 minutes of inactivity in a session. I'm not using any specific settings - just defaults. My SFSB class in the stacktrace is org.jboss.weld.examples.pastecode.session.History 13:40:23,427 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-pastecode]] org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 13:51:08,812 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-pastecode]] Session event listener threw exception: javax.ejb.NoSuchEJBException: Could not find Stateful bean: 3j011-vkamuu-g5s27uvi-1-g5s42hod-ac at org.jboss.ejb3.cache.simple.SimpleStatefulCache.remove(SimpleStatefulCache.java:544) at org.jboss.ejb3.stateful.StatefulContainer.destroySession(StatefulContainer.java:1452) at org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl.destroySession(EndpointImpl.java:61) at org.jboss.weld.integration.ejb.JBossSessionObjectReference.remove(JBossSessionObjectReference.java:62) at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:108) at org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) at org.jboss.weld.examples.pastecode.session.History_$$_javassist_54.destroy(History_$$_javassist_54.java) at org.jboss.weld.bean.SessionBean.destroy(SessionBean.java:329) at org.jboss.weld.context.ForwardingContextual.destroy(ForwardingContextual.java:34) at org.jboss.weld.context.AbstractMapContext.destroy(AbstractMapContext.java:146) at org.jboss.weld.context.AbstractMapContext.destroy(AbstractMapContext.java:163) at org.jboss.weld.context.AbstractThreadLocalMapContext.destroy(AbstractThreadLocalMapContext.java:68) at org.jboss.weld.context.ContextLifecycle.endSession(ContextLifecycle.java:80) at org.jboss.weld.servlet.ServletLifecycle.endSession(ServletLifecycle.java:96) at org.jboss.weld.servlet.WeldListener.sessionDestroyed(WeldListener.java:141) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:686) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:581) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:690) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:675) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1383) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1675) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1684) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1684) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1664) at java.lang.Thread.run(Thread.java:619) -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-436) Lifecycle callback interceptors not invoked for normal scoped managed beans

by Jozef Hartinger (JIRA)

Lifecycle callback interceptors not invoked for normal scoped managed beans --------------------------------------------------------------------------- Key: WELD-436 URL: https://jira.jboss.org/jira/browse/WELD-436 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.CR2 Reporter: Jozef Hartinger Fix For: 1.0.1.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

14 years, 3 months

3
6
0 / 0

[JBoss JIRA] Updated: (WELDINT-4) Use shared library mode in JBoss AS

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-4?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-4: ---------------------------- Fix Version/s: (was: 6.0.0.Beta7) > Use shared library mode in JBoss AS > ----------------------------------- > > Key: WELDINT-4 > URL: https://jira.jboss.org/jira/browse/WELDINT-4 > Project: Weld Integration > Issue Type: Feature Request > Components: Deployer > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELDINT-8) Ensure that all requests to application are not processed until after Web Beans initializaiton is complete

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-8?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-8: ---------------------------- Fix Version/s: (was: 6.0.0.Beta7) > Ensure that all requests to application are not processed until after Web Beans initializaiton is complete > ---------------------------------------------------------------------------------------------------------- > > Key: WELDINT-8 > URL: https://jira.jboss.org/jira/browse/WELDINT-8 > Project: Weld Integration > Issue Type: Feature Request > Components: Deployer > Reporter: 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELDINT-5) Implement ValidatorServices

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-5?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-5: ---------------------------- Fix Version/s: (was: 6.0.0.Beta7) > Implement ValidatorServices > --------------------------- > > Key: WELDINT-5 > URL: https://jira.jboss.org/jira/browse/WELDINT-5 > Project: Weld Integration > Issue Type: Feature Request > Components: JBoss Services > 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2010