September 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-674) Weld Tomcat 7.0.x support

by Davide Malpassini (JIRA)

Weld Tomcat 7.0.x support ------------------------- Key: WELD-674 URL: https://jira.jboss.org/browse/WELD-674 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Environment: Tomcat 7.0.x Reporter: Davide Malpassini Fix For: 1.1.0.Beta2 Tomcat 7 have dropped the AnnotationProcessor and in the latest version uses Instance Manager. So Weld can't bootstrap. -- 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

14 years, 5 months

2
10
0 / 0

[JBoss JIRA] Created: (WELD-675) Add a ServletContext configuration parameter for enabling/disabling automatic session creation in WeldListener/ServletLifecycle

by Marius Bogoevici (JIRA)

Add a ServletContext configuration parameter for enabling/disabling automatic session creation in WeldListener/ServletLifecycle ------------------------------------------------------------------------------------------------------------------------------- Key: WELD-675 URL: https://jira.jboss.org/browse/WELD-675 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Marius Bogoevici Fix For: 1.1.0.Beta2 As noted by Heiko here: http://github.com/weld/core/pull/10 , the ServletListener breaks in some versions of Jetty, since getSession() is unable to create a new Session. However, completely disabling new session creation for the listener changes the way ServletListener behaves, in that the first request hitting a newly started server may not have a sessioncontext/requestcontext/conversationcontext assigned to it. While this can work fine in general, I think that we need some ability to finely tune this, by adding a ServletContext parameter which would control this behaviour (allow new session creation by default, but allow users to turn this off) -- 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

14 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (WELD-681) TypeSafeResolver leaks memory

by Stuart Douglas (JIRA)

TypeSafeResolver leaks memory ------------------------------ Key: WELD-681 URL: https://jira.jboss.org/browse/WELD-681 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.1.0.Beta2 a minor bug in TypeSafeResolver.Key means Resolvers are never released -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-682) Remove TypeSafeResolver.Key

by Stuart Douglas (JIRA)

Remove TypeSafeResolver.Key --------------------------- Key: WELD-682 URL: https://jira.jboss.org/browse/WELD-682 Project: Weld Issue Type: Task Affects Versions: 1.1.0.Beta1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.1.0.Beta2 -- 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

14 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-676) Proxies throw exception when used from many clients at the same time

by Martin Gencur (JIRA)

Proxies throw exception when used from many clients at the same time -------------------------------------------------------------------- Key: WELD-676 URL: https://jira.jboss.org/browse/WELD-676 Project: Weld Issue Type: Bug Components: Proxies Environment: Affected weld version - WELD-000900 1.1.0 (2010-09-09 00:04) Reporter: Martin Gencur This exception arises when running around 7+ clients. The HashComputer component is a stateless session bean. Stacktrace: 2010/09/09 08:29:08:387 EDT [WARN ][Runner - 0] HOST qa05.mw.lab.eng.bos.redhat.com:rootProcess:weld-pastecode-perf - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>JBoss Web/3.0.0-beta-6 - Error report</title><style></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade">type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception <pre>javax.servlet.ServletException: org.jboss.weld.examples.pastecode.session.org$jboss$weld$bean-flat-SessionBean-HashComputer_$$_WeldProxy cannot be cast to org.jboss.weld.conversation.ConversationImpl javax.faces.webapp.FacesServlet.service(FacesServlet.java:325) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:195) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:159) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) </pre>root cause <pre>java.lang.ClassCastException: org.jboss.weld.examples.pastecode.session.org$jboss$weld$bean-flat-SessionBean-HashComputer_$$_WeldProxy cannot be cast to org.jboss.weld.conversation.ConversationImpl org.jboss.weld.servlet.BeanProvider.conversation(BeanProvider.java:65) org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHandler.java:71) com.sun.faces.renderkit.html_basic.FormRenderer.getActionStr(FormRenderer.java:234) com.sun.faces.renderkit.html_basic.FormRenderer.encodeBegin(FormRenderer.java:137) javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:823) javax.faces.component.UIComponent.encodeAll(UIComponent.java:1611) javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616) com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:380) com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:195) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:159) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) -- 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

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-677) ConversationManager throws IllegalArgumentException when running many clients at the same time

by Martin Gencur (JIRA)

ConversationManager throws IllegalArgumentException when running many clients at the same time ---------------------------------------------------------------------------------------------- Key: WELD-677 URL: https://jira.jboss.org/browse/WELD-677 Project: Weld Issue Type: Bug Components: Conversations Environment: Affected weld version - WELD-000900 1.1.0 (2010-09-09 00:04) Reporter: Martin Gencur This exception arises when running around 23+ sessions. Stacktrace: 2010/09/10 02:34:51:045 EDT [WARN ][Runner - 7] HOST qa05.mw.lab.eng.bos.redhat.com:rootProcess:weld-numberguess-perf - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>JBoss Web/3.0.0-beta-6 - Error report</title><style></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade">type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception <pre>javax.servlet.ServletException: Can not set org.jboss.weld.conversation.ConversationManager2 field org.jboss.weld.conversation.ConversationImpl.conversationManager to java.lang.Long javax.faces.webapp.FacesServlet.service(FacesServlet.java:325) org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) </pre>root cause <pre>java.lang.IllegalArgumentException: Can not set org.jboss.weld. conversation.ConversationManager2 field org.jboss.weld.conversation.ConversationImpl.conversationManager to java.lang.Long sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146) sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150) sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) java.lang.reflect.Field.set(Field.java:657) org.jboss.weld.introspector.jlr.WeldFieldImpl.set(WeldFieldImpl.java:95) org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:118) org.jboss.weld.util.Beans.injectBoundFields(Beans.java:840) org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:852) org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:184) org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:54) org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:178) org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:144) org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:172) org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:339) org.jboss.weld.context.AbstractMapContext.get(AbstractMapContext.java:116) org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:89) org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:94) org.jboss.weld.conversation.org$jboss$weld$bean-weld-ManagedBean-class_org$jboss$weld$conversation$ConversationImpl_$$_WeldProxy. isTransient(org$jboss$weld$bean-weld-ManagedBean-class_org$jboss$weld$conversation$ConversationImpl_$$_WeldProxy.java) org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHandler.java:72) com.sun.faces.renderkit.html_basic.FormRenderer.getActionStr(FormRenderer.java:234) com.sun.faces.renderkit.html_basic.FormRenderer.encodeBegin(FormRenderer.java:137) javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:823) javax.faces.component.UIComponent.encodeAll(UIComponent.java:1611) javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616) com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:380) com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) -- 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

14 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (WELDX-96) Support injection of Bean and AnnotatedType

by Stuart Douglas (JIRA)

Support injection of Bean and AnnotatedType -------------------------------------------- Key: WELDX-96 URL: https://jira.jboss.org/jira/browse/WELDX-96 Project: Weld Extensions Issue Type: Feature Request Reporter: Stuart Douglas A bean should be able to inject the corresponding Bean and AnnotatedType (if available) objects in order to inspect changes made to the bean metadata through the SPI. This should also be done for interceptors, however I am not really sure how to do this without a modification to the spec. -- 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-688) Implement a BoundConversationContext

by Pete Muir (JIRA)

Implement a BoundConversationContext ------------------------------------ Key: WELD-688 URL: https://jira.jboss.org/browse/WELD-688 Project: Weld Issue Type: Feature Request Components: Conversations, Scopes & Contexts Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.Beta2 Currently conversations are only implemented for Http environments, a BoundConversationContext will allow conversations backed by an arbitrary map. -- 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

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-451) Allow including the cid in the url to be configurable in <redirect /> in pages.xml

by Samuel Mendenhall (JIRA)

Allow including the cid in the url to be configurable in <redirect /> in pages.xml ---------------------------------------------------------------------------------- Key: WELD-451 URL: https://jira.jboss.org/jira/browse/WELD-451 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.1.CR2 Reporter: Samuel Mendenhall Priority: Minor Fix For: 1.0.1.GA In org.jboss.seam.faces.Navigator.java the includeConversationId variable is currently hardcoded to true. protected void redirect(String viewId, Map<String, Object> parameters, boolean includePageParams) { if ( Strings.isEmpty(viewId) ) { viewId = Pages.getCurrentViewId(); } if ( log.isDebugEnabled() ) log.debug("redirecting to: " + viewId); FacesManager.instance().redirect(viewId, parameters, true, includePageParams); } This should be made configurable so that one can redirect and optionally have the cid not included ie. <redirect view-id="/somePage.xhtml" includeConversationId="false" /> -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-416) Consider whether we should hold destroying the session context until all requests using it have ended

by Pete Muir (JIRA)

Consider whether we should hold destroying the session context until all requests using it have ended ----------------------------------------------------------------------------------------------------- Key: WELD-416 URL: https://jira.jboss.org/jira/browse/WELD-416 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Reporter: Pete Muir Assignee: David Allen 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, 5 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues September 2010