[JBoss JIRA] (SEAMFACES-250) UIInputContainer enclose attribute doesn't work
by Dupont Dupont (JIRA)
Dupont Dupont created SEAMFACES-250:
---------------------------------------
Summary: UIInputContainer enclose attribute doesn't work
Key: SEAMFACES-250
URL: https://issues.jboss.org/browse/SEAMFACES-250
Project: Seam Faces
Issue Type: Feature Request
Reporter: Dupont Dupont
UIInputContainer enclose attribute doesn't work
Using enclose attribute with UIInputContainer should generate an HTML div.
This is not the case.
It is due to the fact that UIInputContainer expects a java.lang.Boolean and jsf implementation return a java.lang.String (see [JAVASERVERFACES-2142|http://java.net/jira/browse/JAVASERVERFACES-2142] and [MYFACES-3027|https://issues.apache.org/jira/browse/MYFACES-3027]).
Also when fixing this issue, there's a possible NPE in startContainerElement() method (style and styleClass can be null when calling .length()).
Sample use case :
Composite
{code:xml}
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:c="http://java.sun.com/jsp/jstl/core"
xmlns:cc="http://java.sun.com/jsf/composite">
<cc:interface componentType="org.jboss.seam.faces.InputContainer">
<cc:attribute name="label" required="true" />
<cc:attribute name="ajax" default="false" />
<cc:attribute name="inputs" default="1" />
<cc:attribute name="labelClass"/>
<cc:attribute name="enclose" default="true"/>
</cc:interface>
<cc:implementation>
<h:outputLabel id="label" for="" styleClass="control-label #{cc.attrs.labelClass}">
<ui:fragment rendered="#{cc.attrs.invalid}">
<i class="icon-msg-err"></i>
</ui:fragment>
#{cc.attrs.label}
<h:panelGroup styleClass="required" rendered="#{cc.attrs.required}">*</h:panelGroup> :
</h:outputLabel>
<div class="controls">
<ui:fragment>
<cc:insertChildren />
</ui:fragment>
<ui:fragment rendered="#{cc.attrs.invalid}">
<p class="help-block"><h:message id="message#{1}" for=""/></p>
</ui:fragment>
</div>
</cc:implementation>
</ui:composition>
{code}
Composite usage :
{code:xml}
<field:edit id="nom" label="#{messages['chargeClientele.nom.label']}">
<h:inputText id="input" value="#{chargeClienteleController.instance.nom}" styleClass="input-small" required="true"/>
</field:edit>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (SOLDER-338) Solder can't still inject HttpServletRequest
by Adam Lukaszewski (JIRA)
[ https://issues.jboss.org/browse/SOLDER-338?page=com.atlassian.jira.plugin... ]
Adam Lukaszewski updated SOLDER-338:
------------------------------------
Attachment: multi_ear_solder_3_1_0.zip
multi_ear_solder_3_1_1.zip
> Solder can't still inject HttpServletRequest
> --------------------------------------------
>
> Key: SOLDER-338
> URL: https://issues.jboss.org/browse/SOLDER-338
> Project: Solder
> Issue Type: Bug
> Components: Servlet
> Affects Versions: 3.1.0.Final
> Environment: JBoss 7.1.1
> Reporter: Adam Lukaszewski
> Labels: solder
> Attachments: multi_ear_solder_3_1_0.zip, multi_ear_solder_3_1_1.zip
>
>
> Executing identity.logout will cause an java.lang.IllegalStateException: Attempted to inject an HttpSession before it has been initialized.
> Before I go into more details I would like to describe some of the main findings on that issue and objectives that I want to establish. Since I am working on an bigger j2ee project, I decided to package the application as ear. One of the further claims was to include a web framework that can ease some of the repetitive tasks that developers are faced programming this kind applications. I have made my choice: Seam 3.x.x should be the one!
> With this ideas in mind I started to develop a small ear application with embedded seam (which should be the starting point of the adventure). Everything seams to work perfectly until I have been playing a little bit around with the seam-booking example. In order to understand seam and its opportunities better I have decided to port the seam-booking app into my ear structure. Everything worked very well until I started to implement the authentication mechanism. Logging out from the system causes the above exception.
> Although I have found a solder-issue (solder-311) and a forum post (https://community.jboss.org/message/735049) I could not find any solution (completely equal to my problem). The issue suggests to update to solder-3.1.1 which should fix the problem but it doesn't!
> Since I have got some deeper insights of packaging seam into an ear project I would like to share this intermediate results (maybe to come to a solution).
> Attached you will find two projects.
> multi_ear_solder_3_1_0.zip and multi_ear_solder_3_1_1.zip.
> Both projects are ear applications with some (unfinished) business logic from the seam-booking example. The difference, as you maybe expect, is the solder version I am using. Hitting the localhost:8080/multi-web should bring you to the app. Login as shane (password: 12345) and try to logout again by clicking the logout link, then you will see the error regardless which seam version you use.
> Although, I think that seam is a perfect artifact in that context my development progress stops through this problem. Does anyone have an idea how to figure this issue out? Do you think that the authentication module is only effected by this problem or will be there also some issues with the other modules (like remote, social, jsf,...)? I think the latter one is to be expected, isn't it?
> A appreciate any kind of help.
> Cheers,
> Adam L.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (SOLDER-338) Solder can't still inject HttpServletRequest
by Adam Lukaszewski (JIRA)
Adam Lukaszewski created SOLDER-338:
---------------------------------------
Summary: Solder can't still inject HttpServletRequest
Key: SOLDER-338
URL: https://issues.jboss.org/browse/SOLDER-338
Project: Solder
Issue Type: Bug
Components: Servlet
Affects Versions: 3.1.0.Final
Environment: JBoss 7.1.1
Reporter: Adam Lukaszewski
Executing identity.logout will cause an java.lang.IllegalStateException: Attempted to inject an HttpSession before it has been initialized.
Before I go into more details I would like to describe some of the main findings on that issue and objectives that I want to establish. Since I am working on an bigger j2ee project, I decided to package the application as ear. One of the further claims was to include a web framework that can ease some of the repetitive tasks that developers are faced programming this kind applications. I have made my choice: Seam 3.x.x should be the one!
With this ideas in mind I started to develop a small ear application with embedded seam (which should be the starting point of the adventure). Everything seams to work perfectly until I have been playing a little bit around with the seam-booking example. In order to understand seam and its opportunities better I have decided to port the seam-booking app into my ear structure. Everything worked very well until I started to implement the authentication mechanism. Logging out from the system causes the above exception.
Although I have found a solder-issue (solder-311) and a forum post (https://community.jboss.org/message/735049) I could not find any solution (completely equal to my problem). The issue suggests to update to solder-3.1.1 which should fix the problem but it doesn't!
Since I have got some deeper insights of packaging seam into an ear project I would like to share this intermediate results (maybe to come to a solution).
Attached you will find two projects.
multi_ear_solder_3_1_0.zip and multi_ear_solder_3_1_1.zip.
Both projects are ear applications with some (unfinished) business logic from the seam-booking example. The difference, as you maybe expect, is the solder version I am using. Hitting the localhost:8080/multi-web should bring you to the app. Login as shane (password: 12345) and try to logout again by clicking the logout link, then you will see the error regardless which seam version you use.
Although, I think that seam is a perfect artifact in that context my development progress stops through this problem. Does anyone have an idea how to figure this issue out? Do you think that the authentication module is only effected by this problem or will be there also some issues with the other modules (like remote, social, jsf,...)? I think the latter one is to be expected, isn't it?
A appreciate any kind of help.
Cheers,
Adam L.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (SOLDER-311) HttpServletRequest cannot be @Inject-ed
by Adam Lukaszewski (JIRA)
[ https://issues.jboss.org/browse/SOLDER-311?page=com.atlassian.jira.plugin... ]
Adam Lukaszewski commented on SOLDER-311:
-----------------------------------------
Hi,
I've got still the problem with the HttpServletRequest. Can't fix it... I've also replaced the solder 3.1.0 version against the 3.1.1 and still getting the same Exception (@Zimmermann: Have you done something additionally, you haven't mentioned?)
Does anyone have an idea, a hint how to figure that problem out? I've spend a lot of time with the configuration of my ear with seam and while I have beeing trying a little bit around with the seam-booking example I ran into this issue.
Thanks for your support. Cheers,
Adam
> HttpServletRequest cannot be @Inject-ed
> ---------------------------------------
>
> Key: SOLDER-311
> URL: https://issues.jboss.org/browse/SOLDER-311
> Project: Solder
> Issue Type: Bug
> Components: Servlet
> Affects Versions: 3.1.0.Final
> Environment: JBossAS 7.1beta1b
> Reporter: Juergen Zimmermann
> Attachments: testcase.ear.zip, testcase.src.zip
>
>
> "@Inject HttpServletRequest request;" results in the stacktrace below, when I invoke "request(myusername, mypassword);" using JBossAS 7.1beta1b. I'll attach a testcase as an EAR. Just invoke http://localhost:8080/testcase and you'll see a form where you click the OK button. Then you'll see the stacktrace in the JBoss console.
> Stacktrace:
> 09:11:00,535 Warnung [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--127.0.0.1-8080-1) #{cust.findCustomer}: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest(): javax.faces.FacesException: #{cust.findCustomer}: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()
> at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.3.Final.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.4.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.3.Final.jar:]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:126) [prettyfaces-jsf2-3.3.2.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.3.Final.jar:]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Beta1b.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:151) [jboss-as-web-7.1.0.Beta1b.jar:]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.3.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.3.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.3.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.3.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.3.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [:1.7.0_02]
> Caused by: javax.faces.el.EvaluationException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()
> at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> ... 28 more
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()
> at org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:217) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:300) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.proxies.HttpServletRequest$83012492$Proxy$_$$_WeldClientProxy.login(HttpServletRequest$83012492$Proxy$_$$_WeldClientProxy.java)
> at testcase.CustomerController.findCustomer(CustomerController.java:43) [classes:]
> at testcase.CustomerController$Proxy$_$$_WeldClientProxy.findCustomer(CustomerController$Proxy$_$$_WeldClientProxy.java) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.7.0_02]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.7.0_02]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.7.0_02]
> at java.lang.reflect.Method.invoke(Method.java:601) [:1.7.0_02]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.3.Final.jar:]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.3.Final.jar:]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.4.Final.jar:]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.4.Final.jar:]
> at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:]
> at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:]
> ... 29 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBSEAM-5067) ConcurrentModificationException in ServerConversationContext.flush()
by Andrey Zhemoytuk (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5067?page=com.atlassian.jira.plugi... ]
Andrey Zhemoytuk updated JBSEAM-5067:
-------------------------------------
Description:
The exception fails after render response phase if long running conversation is active and a bean in conversation scope (additions map) has page/conversation/session scoped outjection.
Latest 2.3.1.CR1-SNAPSHOT (with JBSEAM-5045 fix): The same exception fails in ExceptionFilter after unhandled exception when there is active long running conversation and a component in conversation scope with a page scoped injection.
The issue is not reproducible if http://java.net/jira/browse/JAVASERVERFACES-1685 is reverted. Call to equals in com.sun.faces.context.SessionMap#put (lines 132-138) introduced with 1685 fix causes injection/outjection to occur:
boolean doSet = true;
if (null != value && null != result) {
doSet = ! result.equals(value);
}
if (doSet) {
session.setAttribute(key, value);
}
Stacktrace:
2013-01-09 05:09:26,576 WARN [org.jboss.seam.jsf.SeamPhaseListener] (http--0.0.0.0-8543-1) uncaught exception, passing to exception handler: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:834) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:832) [rt.jar:1.6.0_30]
at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:302) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:410) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:129) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:518) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:248) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:195) [jboss-seam.jar:2.3.0.Final]
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final]
was:
The exception fails after render response phase if long running conversation is active and a bean in conversation scope (additions map) has either page scoped injection or page/conversation/session scoped outjection.
The issue is not reproducible if http://java.net/jira/browse/JAVASERVERFACES-1685 is reverted. Call to equals in com.sun.faces.context.SessionMap#put (lines 132-138) introduced with 1685 fix causes injection/outjection to occur:
boolean doSet = true;
if (null != value && null != result) {
doSet = ! result.equals(value);
}
if (doSet) {
session.setAttribute(key, value);
}
Stacktrace:
2013-01-09 05:09:26,576 WARN [org.jboss.seam.jsf.SeamPhaseListener] (http--0.0.0.0-8543-1) uncaught exception, passing to exception handler: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:834) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:832) [rt.jar:1.6.0_30]
at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:302) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:410) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:129) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:518) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:248) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:195) [jboss-seam.jar:2.3.0.Final]
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final]
> ConcurrentModificationException in ServerConversationContext.flush()
> --------------------------------------------------------------------
>
> Key: JBSEAM-5067
> URL: https://issues.jboss.org/browse/JBSEAM-5067
> Project: Seam 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3.0.Final
> Environment: JBoss AS 7.1.0.Final (JSF RI 2.1.5)
> Reporter: Andrey Zhemoytuk
>
> The exception fails after render response phase if long running conversation is active and a bean in conversation scope (additions map) has page/conversation/session scoped outjection.
> Latest 2.3.1.CR1-SNAPSHOT (with JBSEAM-5045 fix): The same exception fails in ExceptionFilter after unhandled exception when there is active long running conversation and a component in conversation scope with a page scoped injection.
> The issue is not reproducible if http://java.net/jira/browse/JAVASERVERFACES-1685 is reverted. Call to equals in com.sun.faces.context.SessionMap#put (lines 132-138) introduced with 1685 fix causes injection/outjection to occur:
> boolean doSet = true;
> if (null != value && null != result) {
> doSet = ! result.equals(value);
> }
> if (doSet) {
> session.setAttribute(key, value);
> }
> Stacktrace:
> 2013-01-09 05:09:26,576 WARN [org.jboss.seam.jsf.SeamPhaseListener] (http--0.0.0.0-8543-1) uncaught exception, passing to exception handler: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [rt.jar:1.6.0_30]
> at java.util.HashMap$EntryIterator.next(HashMap.java:834) [rt.jar:1.6.0_30]
> at java.util.HashMap$EntryIterator.next(HashMap.java:832) [rt.jar:1.6.0_30]
> at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:302) [jboss-seam.jar:2.3.0.Final]
> at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:410) [jboss-seam.jar:2.3.0.Final]
> at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:129) [jboss-seam.jar:2.3.0.Final]
> at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:518) [jboss-seam.jar:2.3.0.Final]
> at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:248) [jboss-seam.jar:2.3.0.Final]
> at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:195) [jboss-seam.jar:2.3.0.Final]
> at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBSEAM-5067) ConcurrentModificationException in ServerConversationContext.flush()
by Andrey Zhemoytuk (JIRA)
Andrey Zhemoytuk created JBSEAM-5067:
----------------------------------------
Summary: ConcurrentModificationException in ServerConversationContext.flush()
Key: JBSEAM-5067
URL: https://issues.jboss.org/browse/JBSEAM-5067
Project: Seam 2
Issue Type: Bug
Components: Core
Affects Versions: 2.3.0.Final
Environment: JBoss AS 7.1.0.Final (JSF RI 2.1.5)
Reporter: Andrey Zhemoytuk
The exception fails after render response phase if long running conversation is active and a bean in conversation scope (additions map) has either page scoped injection or page/conversation/session scoped outjection.
The issue is not reproducible if http://java.net/jira/browse/JAVASERVERFACES-1685 is reverted. Call to equals in com.sun.faces.context.SessionMap#put (lines 132-138) introduced with 1685 fix causes injection/outjection to occur:
boolean doSet = true;
if (null != value && null != result) {
doSet = ! result.equals(value);
}
if (doSet) {
session.setAttribute(key, value);
}
Stacktrace:
2013-01-09 05:09:26,576 WARN [org.jboss.seam.jsf.SeamPhaseListener] (http--0.0.0.0-8543-1) uncaught exception, passing to exception handler: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:834) [rt.jar:1.6.0_30]
at java.util.HashMap$EntryIterator.next(HashMap.java:832) [rt.jar:1.6.0_30]
at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:302) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:410) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:129) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:518) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:248) [jboss-seam.jar:2.3.0.Final]
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:195) [jboss-seam.jar:2.3.0.Final]
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBSEAM-4752) A chatroom example works only in Firefox web browser
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-4752?page=com.atlassian.jira.plugi... ]
Marek Novotny commented on JBSEAM-4752:
---------------------------------------
this is very old issue, but before I close this I need to check it if it is outdated or not.
> A chatroom example works only in Firefox web browser
> -----------------------------------------------------
>
> Key: JBSEAM-4752
> URL: https://issues.jboss.org/browse/JBSEAM-4752
> Project: Seam 2
> Issue Type: Bug
> Components: Examples
> Affects Versions: 2.2.1.CR3
> Environment: JBossAS 4, JBossAS 5
> Reporter: Martin Gencur
> Assignee: Marek Novotny
> Fix For: The future
>
>
> When playing with the application, nothing shows in the main area for messages if the web browser is different from Firefox. I tried both Opera 10.00 and Chromium web browser 5.0.342.9.
> JBossAS console log throws the following:
> 12:42:19,486 ERROR [Remoting] Error
> javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context.
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:96)
> at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:65)
> at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
> at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
> at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context.
> at org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:169)
> at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:43)
> at org.jboss.seam.remoting.PollHandler$1.process(PollHandler.java:72)
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:65)
> ... 36 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBSEAM-4752) A chatroom example works only in Firefox web browser
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-4752?page=com.atlassian.jira.plugi... ]
Marek Novotny reassigned JBSEAM-4752:
-------------------------------------
Assignee: Marek Novotny
> A chatroom example works only in Firefox web browser
> -----------------------------------------------------
>
> Key: JBSEAM-4752
> URL: https://issues.jboss.org/browse/JBSEAM-4752
> Project: Seam 2
> Issue Type: Bug
> Components: Examples
> Affects Versions: 2.2.1.CR3
> Environment: JBossAS 4, JBossAS 5
> Reporter: Martin Gencur
> Assignee: Marek Novotny
> Fix For: The future
>
>
> When playing with the application, nothing shows in the main area for messages if the web browser is different from Firefox. I tried both Opera 10.00 and Chromium web browser 5.0.342.9.
> JBossAS console log throws the following:
> 12:42:19,486 ERROR [Remoting] Error
> javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context.
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:96)
> at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:65)
> at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
> at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
> at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context.
> at org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:169)
> at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:43)
> at org.jboss.seam.remoting.PollHandler$1.process(PollHandler.java:72)
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:65)
> ... 36 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBSEAM-5052) s:selectItems noSelectionLabel causes errors without using ui:debug
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5052?page=com.atlassian.jira.plugi... ]
Marek Novotny reopened JBSEAM-5052:
-----------------------------------
> s:selectItems noSelectionLabel causes errors without using ui:debug
> --------------------------------------------------------------------
>
> Key: JBSEAM-5052
> URL: https://issues.jboss.org/browse/JBSEAM-5052
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Controls
> Affects Versions: 2.2.1.Final, 2.2.2.Final, 2.3.0.Final
> Environment: JBoss AS 7.1.1
> Reporter: Andrew Wheeler
> Assignee: Marek Novotny
> Labels: jsf2
> Fix For: 2.3.1.CR1
>
> Attachments: UISelectItems.java
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> UI example of <s:selectItems> can show this issue when <ui:debug> is removed from examples/ui/ui-web/src/main/webapp/template.xhtml.
> The converter "org.jboss.sema.ui.NoSelectionConverter" is not firing when rendering the page. Converters are however fired for other selectOneMenu items on the page that have one or more items.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months