December 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (SOLDER-337) Solder doesn't work with 7.1.3 and 7.2.0.alpha1-SNAPSHOT

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/SOLDER-337?page=com.atlassian.jira.plugin... ] Stuart Douglas moved AS7-6146 to SOLDER-337: -------------------------------------------- Project: Solder (was: Application Server 7) Key: SOLDER-337 (was: AS7-6146) Affects Version/s: (was: 7.2.0.Alpha1) (was: 7.1.3.Final (EAP)) Component/s: (was: CDI / Weld) > Solder doesn't work with 7.1.3 and 7.2.0.alpha1-SNAPSHOT > -------------------------------------------------------- > > Key: SOLDER-337 > URL: https://issues.jboss.org/browse/SOLDER-337 > Project: Solder > Issue Type: Bug > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Attachments: testcase.zip > > > The attached testcase results in a NPE in a JBoss Solder class when it is deployed to 7.1.3.Final and also to 7.2.0.alpha1-SNAPSHOT. It works fine with 7.1.2.Final. > Just do a "mvn package jboss-as:deploy" to invoke the testcase. The testcase is preconfigured for 7.1.3. To switch to 7.1.2 or 7.2.0.alpha1 the related property is in the beginning of pom.xml > I'm not sure whether the issue is related to Weld (1.1.8 inside JBoss 7.1.2, 1.1.9 inside JBoss 7.1.3, 1.1.10 inside JBoss 7.2) or whether the issue is related to Solder. Anyway, this issue prevents an upgrade from JBoss 7.1.2. > The stacktrace in the JBoss console: > ... > INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] Wrapping InjectionTarget to set field values: test.ArticleController > ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.deployment.unit."test.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > java.lang.NullPointerException > at org.jboss.solder.bean.generic.GenericBeanExtension.registerGenericBeanObserverMethod(GenericBeanExtension.java:378) > at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:117) > at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:85) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:75) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:60) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) > at org.jboss.weld.bootstrap.events.ProcessObserverMethodImpl.fire(ProcessObserverMethodImpl.java:45) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:76) > at org.richfaces.cdi.push.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:360) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:40) > at org.jboss.weld.bootstrap.events.ProcessObserverMethodImpl.fire(ProcessObserverMethodImpl.java:45) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:76) > at org.richfaces.cdi.push.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:360) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Schmidt updated JBSEAM-5064: ---------------------------------- Workaround Description: Add inside the s:link/s:button <s:conversationPropagation type="none"/> > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5064: ------------------------------------- Summary: s:link conversation propagation none broken Key: JBSEAM-5064 URL: https://issues.jboss.org/browse/JBSEAM-5064 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.3.1.CR1 Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT Reporter: Marek Schmidt Assignee: Marek Novotny Priority: Critical Fix For: 2.3.1.CR1 s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (SOLDER-311) HttpServletRequest cannot be @Inject-ed

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/SOLDER-311?page=com.atlassian.jira.plugin... ] Juergen Zimmermann closed SOLDER-311. ------------------------------------- Resolution: Out of Date The issue is gone since 3.1.1 > 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

12 years

1
0
0 / 0

[JBoss JIRA] (SEAMREST-43) Filter for Transaction start/stop

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/SEAMREST-43?page=com.atlassian.jira.plugi... ] Juergen Zimmermann closed SEAMREST-43. -------------------------------------- Resolution: Won't Fix Just add the JARs of Seam Faces during deployment. > Filter for Transaction start/stop > --------------------------------- > > Key: SEAMREST-43 > URL: https://issues.jboss.org/browse/SEAMREST-43 > Project: Seam REST > Issue Type: Feature Request > Components: Persistence > Affects Versions: 3.0.0.Final > Reporter: Juergen Zimmermann > > It would be helpful if SEAM REST could provide a filter which could be defined in web.xml: > Start a Transaction before the processing in a Resource class' method is started, and stop the transaction when the processing of the Resource method is done. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5045) Ajax error not calling ExceptionFilter

by Tiago Peruzzo (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5045?page=com.atlassian.jira.plugi... ] Tiago Peruzzo updated JBSEAM-5045: ---------------------------------- Attachment: MockExternalContext.java > Ajax error not calling ExceptionFilter > -------------------------------------- > > Key: JBSEAM-5045 > URL: https://issues.jboss.org/browse/JBSEAM-5045 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Tiago Peruzzo > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: ErrorHandlingTest.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, patch.zip > > > Now that JSF2 now has support for Ajax errors Ajax requests are being processed by the JSF and not being thrown exceptions to the Seam ExceptionFilter capture. > {code:xml} > <exception log="true" log-level="fatal"> > <end-conversation before-redirect="true" root="true"/> > <redirect view-id="/error.xhtml"> > <message severity="fatal">Unexpected error, please try again.</message> > </redirect> > </exception> > {code} > {code:xml} > <h:form> > <h:commandButton action="#{xxxx.xxxxx}" value="Submit"/> > <h:commandButton action="#{xxxx.xxxxx}" value="Ajax Submit"> > <f:ajax /> > </h:commandButton> > </h:form> > {code} > I even did a patch that still support the redirection to the error pages in AJAX requests. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5045) Ajax error not calling ExceptionFilter

by Tiago Peruzzo (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5045?page=com.atlassian.jira.plugi... ] Tiago Peruzzo updated JBSEAM-5045: ---------------------------------- Attachment: ErrorHandlingTest.java MockExternalContext.java > Ajax error not calling ExceptionFilter > -------------------------------------- > > Key: JBSEAM-5045 > URL: https://issues.jboss.org/browse/JBSEAM-5045 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Tiago Peruzzo > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: ErrorHandlingTest.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, patch.zip > > > Now that JSF2 now has support for Ajax errors Ajax requests are being processed by the JSF and not being thrown exceptions to the Seam ExceptionFilter capture. > {code:xml} > <exception log="true" log-level="fatal"> > <end-conversation before-redirect="true" root="true"/> > <redirect view-id="/error.xhtml"> > <message severity="fatal">Unexpected error, please try again.</message> > </redirect> > </exception> > {code} > {code:xml} > <h:form> > <h:commandButton action="#{xxxx.xxxxx}" value="Submit"/> > <h:commandButton action="#{xxxx.xxxxx}" value="Ajax Submit"> > <f:ajax /> > </h:commandButton> > </h:form> > {code} > I even did a patch that still support the redirection to the error pages in AJAX requests. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5045) Ajax error not calling ExceptionFilter

by Tiago Peruzzo (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5045?page=com.atlassian.jira.plugi... ] Tiago Peruzzo commented on JBSEAM-5045: --------------------------------------- Marek, I made a new patch now using dom4j to assemble XML because I needed to make an escape in cases where it url to contain special characters. I also made a simple test case that reproduces this error. > Ajax error not calling ExceptionFilter > -------------------------------------- > > Key: JBSEAM-5045 > URL: https://issues.jboss.org/browse/JBSEAM-5045 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Tiago Peruzzo > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: ErrorHandlingTest.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, MockExternalContext.java, patch.zip > > > Now that JSF2 now has support for Ajax errors Ajax requests are being processed by the JSF and not being thrown exceptions to the Seam ExceptionFilter capture. > {code:xml} > <exception log="true" log-level="fatal"> > <end-conversation before-redirect="true" root="true"/> > <redirect view-id="/error.xhtml"> > <message severity="fatal">Unexpected error, please try again.</message> > </redirect> > </exception> > {code} > {code:xml} > <h:form> > <h:commandButton action="#{xxxx.xxxxx}" value="Submit"/> > <h:commandButton action="#{xxxx.xxxxx}" value="Ajax Submit"> > <f:ajax /> > </h:commandButton> > </h:form> > {code} > I even did a patch that still support the redirection to the error pages in AJAX requests. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5062) Seam example ant scripts should be pure ant scripts

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5062?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5062: --------------------------------- Git Pull Request: https://github.com/seam2/jboss-seam/pull/1 Github pull request attached. > Seam example ant scripts should be pure ant scripts > --------------------------------------------------- > > Key: JBSEAM-5062 > URL: https://issues.jboss.org/browse/JBSEAM-5062 > Project: Seam 2 > Issue Type: Feature Request > Components: Build > Affects Versions: 2.3.0.Final > Reporter: Marek Novotny > Assignee: Vaclav Dedik > Priority: Critical > Fix For: 2.3.1.CR1 > > > Booking, Seamspace and Dvdstore examples has got ant scripts for presenting Ant usage for backward compatible way of building. > These scripts are using Maven like build structure with hardcoded dependency versions. We need to use/include pom.xml dependencies and not hardcoded versions in build.xml. Next we need to use one Ant script file rather than including all submodule ant scripts into parent script. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5063) Debug page broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5063?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5063. ----------------------------------- Assignee: Marek Novotny Resolution: Done fixed by re-adding of DebugRedirect component class - https://github.com/seam2/jboss-seam/commit/d18acd0874bf14e56a4211aeeceeb8... > Debug page broken > ----------------- > > Key: JBSEAM-5063 > URL: https://issues.jboss.org/browse/JBSEAM-5063 > Project: Seam 2 > Issue Type: Bug > Components: Framework > Affects Versions: 2.3.0.Final > Environment: Seam 2.3.0.Final > Reporter: Javier Rodriguez > Assignee: Marek Novotny > Labels: debug, page > Fix For: 2.3.1.CR1 > > > Debug page's conversations table, 'destroy' link is broken. It try to access component {{org.jboss.seam.debug.jsf.debugRedirect}}, which does not exists in Seam 2.3.0.Final version... > The result is: > {code:title=error message} > Exception during request processing: > Caused by javax.servlet.ServletException with message: "/debug.xhtml @111,124 target="#{org.jboss.seam.debug.jsf.debugRedirect.viewId}": Target Unreachable, 'jsf' returned null on 'org.jboss.seam.Namespace'" > {code} > each time you click conversation's destroy link. -- 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

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2012