February 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5077. ----------------------------------- Resolution: Done fixed > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5074) Excel example SeamTest failure UnsupportedOperationException in ExternalContext.getRequestCharacterEncoding

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5074?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5074: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done PR was merged > Excel example SeamTest failure UnsupportedOperationException in ExternalContext.getRequestCharacterEncoding > ----------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-5074 > URL: https://issues.jboss.org/browse/JBSEAM-5074 > Project: Seam 2 > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.3.1.CR1 > Environment: Seam 2.3.1-SNAPSHOT, AS 7.2.0.Alpha1-SNAPSHOT (2013-02-08) > Reporter: Marek Schmidt > Assignee: Marek Schmidt > Fix For: 2.3.1.CR1 > > > Excel SeamTest failure: > {noformat} > Caused by: java.lang.UnsupportedOperationException > at javax.faces.context.ExternalContext.getRequestCharacterEncoding(ExternalContext.java:945) > at com.sun.faces.facelets.compiler.SAXCompiler.getEncoding(SAXCompiler.java:453) > at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:420) > at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:401) > at com.sun.faces.facelets.compiler.Compiler.compile(Compiler.java:124) > at com.sun.faces.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:304) > at com.sun.faces.facelets.impl.DefaultFaceletFactory.access$100(DefaultFaceletFactory.java:92) > at com.sun.faces.facelets.impl.DefaultFaceletFactory$1.newInstance(DefaultFaceletFactory.java:159) > at com.sun.faces.facelets.impl.DefaultFaceletFactory$1.newInstance(DefaultFaceletFactory.java:157) > at com.sun.faces.facelets.impl.DefaultFaceletCache$1.newInstance(DefaultFaceletCache.java:83) > at com.sun.faces.facelets.impl.DefaultFaceletCache$1.newInstance(DefaultFaceletCache.java:78) > at com.sun.faces.util.ExpiringConcurrentCache$1.call(ExpiringConcurrentCache.java:99) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at com.sun.faces.util.ExpiringConcurrentCache.get(ExpiringConcurrentCache.java:114) > at com.sun.faces.facelets.impl.DefaultFaceletCache.getFacelet(DefaultFaceletCache.java:121) > at com.sun.faces.facelets.impl.DefaultFaceletCache.getFacelet(DefaultFaceletCache.java:62) > at com.sun.faces.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:255) > at org.jboss.seam.ui.facelet.RendererRequest.faceletForViewId(RendererRequest.java:128) > at org.jboss.seam.ui.facelet.RendererRequest.run(RendererRequest.java:106) > at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:43) > at org.jboss.seam.example.excel.test.RenderTest$1.invokeApplication(RenderTest.java:62) > at org.jboss.seam.mock.AbstractSeamTest$Request.invokeApplicationPhase(AbstractSeamTest.java:664) > at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:613) > at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:184) > at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:513) > ... 127 more > {noformat} -- 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, 9 months

1
0
0 / 0

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

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5045?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5045. ----------------------------------- Resolution: Done > 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 > Priority: Critical > 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

11 years, 9 months

1
0
0 / 0

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

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5045?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5045: --------------------------------------- At the end I removed the SeamExceptionHandlerFactory and used bundled JSF javax.faces.webapp.PreJsf2ExceptionHandlerFactory for the old behaviour. > 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 > Priority: Critical > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5073) Programmatic redirect always add conversation id

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5073?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5073. --------------------------------- Resolution: Duplicate Issue fixed by provided patch from JBSEAM-5066 > Programmatic redirect always add conversation id > ------------------------------------------------ > > Key: JBSEAM-5073 > URL: https://issues.jboss.org/browse/JBSEAM-5073 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.1.CR1 > Environment: Seam 2.3.1-SNAPSHOT (2013-01-31) > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > Seam redirect always propagates conversation, even when explicitly told not to. The following code works in Seam 2.2, but now it redirects with the conversation id: > {code} > Redirect redirect = Redirect.instance(); > redirect.setConversationPropagationEnabled(false); > redirect.setViewId("/output.xhtml"); > redirect.execute(); > {code} > This also propagates conversation: > {code} > FacesManager.instance().redirect("/output.xhtml", null, false, false); > {code} > The problem is likely in SeamViewHandler, which adds the cids. even with redirects. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5066) Incorrect Redirection

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5066?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5066. ----------------------------------- Resolution: Done patch applied, thanks Tiago! > Incorrect Redirection > --------------------- > > Key: JBSEAM-5066 > URL: https://issues.jboss.org/browse/JBSEAM-5066 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Environment: 2.3.1-SNAPSHOT > Reporter: Tiago Peruzzo > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: patch.zip > > > After the changes in SeamViewHandler all url's were with conversationId, however in some cases redirect rules exist that may not need to have conversationId in url. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5066) Incorrect Redirection

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5066?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5066: ---------------------------------- Affects Version/s: (was: 2.3.1.CR1) Environment: 2.3.1-SNAPSHOT Component/s: JSF Integration > Incorrect Redirection > --------------------- > > Key: JBSEAM-5066 > URL: https://issues.jboss.org/browse/JBSEAM-5066 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Environment: 2.3.1-SNAPSHOT > Reporter: Tiago Peruzzo > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: patch.zip > > > After the changes in SeamViewHandler all url's were with conversationId, however in some cases redirect rules exist that may not need to have conversationId in url. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Lars Hedman (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Lars Hedman commented on JBSEAM-5077: ------------------------------------- Jens, Many thanks for the workaround, that helped me a lot! /Lars > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Jens Westermann (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Jens Westermann edited comment on JBSEAM-5077 at 2/27/13 9:34 AM: ------------------------------------------------------------------ We need to use the SNAPSHOT version in your development and this temporary fix will solve the problem: import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } was (Author: jan.daces): We need to ust the SNAPSHOT Version in your Development and this temporary fix will solve the Problem: import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Jens Westermann (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Jens Westermann edited comment on JBSEAM-5077 at 2/27/13 9:33 AM: ------------------------------------------------------------------ We need to ust the SNAPSHOT Version in your Development and this temporary fix will solve the Problem: import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } was (Author: jan.daces): import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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, 9 months

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 February 2013