August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2600) Exception handling - Fix the exception handling in Seam

by Shane Bryzak (JIRA)

Exception handling - Fix the exception handling in Seam ------------------------------------------------------- Key: JBSEAM-2600 URL: http://jira.jboss.com/jira/browse/JBSEAM-2600 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Currently we have at least one serious race condition in our pages.xml exception handling, related to redirect/message passing. I can reproduce (JIRA case is open) lost messages on exception redirect. Also, clean up the #{exception} and #{handledException} stuff - which might fix the issue as a side effect. I want one exception instance I can access in EL, not two. I want to be able to call getRootCause() on it to unwrap the root exception. Of course the root cause is the one I specify in pages.xml as the one that is handled, but the #{exception} should always be the wrapper. In any case, a clear and reliable (working in all situations) strategy needs to apply here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2595) Exception handling - Never swallow an exception

by Shane Bryzak (JIRA)

Exception handling - Never swallow an exception ----------------------------------------------- Key: JBSEAM-2595 URL: http://jira.jboss.com/jira/browse/JBSEAM-2595 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA For example, if an action throws NPE, the exception handler checks what is defined in pages.xml. If no handler is defined, SeamPhaseListener swallows the exception after printing it in the log. This is a bad strategy, as most users start with no exception handling defined and no pages.xml, yet they don't see their exceptions on the page. We need SOME default handler, even if no pages.xml is present. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3345) Seam buttons don't render path in relative images

by Jorge Rodr??guez Pedrianes (JIRA)

Seam buttons don't render path in relative images ------------------------------------------------- Key: JBSEAM-3345 URL: https://jira.jboss.org/jira/browse/JBSEAM-3345 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1, 2.1.0.A1, 2.0.3.CR1 Environment: Seam 2.0.3.CR1 Reporter: Jorge Rodr??guez Pedrianes Hello! Using s:button i see that when i try to use a image attribute this don't put the relative paht of my application in de generated code. For example: <s:button image="/resources/images/icons/edit.gif" value="Edit" action="#{bean.action}" type="button" /> but this render: <input src="/resources/images/icons/edit.gif ...> I think that must render this: <input src="/My-Request-Context-Path/resources/images/icons/edit.gif ...> In doEncodeBegin Method of ButtonRendererBase class you can see that don't transform the image URL. A solution is encode the url. For example: private static String src(FacesContext context, UIButton uiButton) { String image = uiButton.getImage(); if (image == null) { return ""; } image = context.getApplication().getViewHandler().getResourceURL(context, image); return (context.getExternalContext().encodeResourceURL(image)); } And then in doEncodeBegin make this: ... if (button.getImage() != null) { writer.writeAttribute(HTML.SRC_ATTR, src(context, button), HTML.SRC_ATTR); } ... Thanks -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3356) Seam PDF integration should throw runtime exceptions, not IOExceptions

by Pete Muir (JIRA)

Seam PDF integration should throw runtime exceptions, not IOExceptions ---------------------------------------------------------------------- Key: JBSEAM-3356 URL: https://jira.jboss.org/jira/browse/JBSEAM-3356 Project: Seam Issue Type: Task Components: PDF Reporter: Pete Muir Overloading IOException like that is nasty -- 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

17 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3351) Security XSD missing elements

by Vinicius Carvalho (JIRA)

Security XSD missing elements ----------------------------- Key: JBSEAM-3351 URL: https://jira.jboss.org/jira/browse/JBSEAM-3351 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Vinicius Carvalho Priority: Minor Well, it seems that the XSD is missing the following elements: permission-manager rule-based-permission-resolver persistent-permission-resolver Well, the app works fine, but eclipse lacks auto-complete ;) -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3353) "version" column in db table induces an @Version hibernate annotation

by Richard Ferrante (JIRA)

"version" column in db table induces an @Version hibernate annotation --------------------------------------------------------------------- Key: JBSEAM-3353 URL: https://jira.jboss.org/jira/browse/JBSEAM-3353 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: Mac OSX 10.5.4 Reporter: Richard Ferrante One of my tables has a column named version create table algorithm_info( id int not null auto_increment, name VARCHAR(255) not null, description VARCHAR(1024) not null, version VARCHAR(255), .... This generated the annotation @Version @Column(name = "version") public String getVersion() { return this.version; } public void setVersion(String version) { this.version = version; } which caused the application to choke on startup Problem solved by removing the "@Version" annotation -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3341) add support for facet name="footer" in <e:column>

by Vladimir Kovalyuk (JIRA)

add support for facet name="footer" in <e:column> ------------------------------------------------- Key: JBSEAM-3341 URL: https://jira.jboss.org/jira/browse/JBSEAM-3341 Project: Seam Issue Type: Feature Request Components: Excel Affects Versions: 2.1.0.BETA1 Environment: any Reporter: Vladimir Kovalyuk <e:column> <f:facet name="header"> <e:cell templates="header" value="#{column.name}" /> </f:facet> <e:cell value="#{column.value}" /> <f:facet name="footer"> <e:cell templates="footer" value="#{column.total}" /> </f:facet> </e:column> -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2952) Icefaces example hotel search conversation timeouts

by Jay Balunas (JIRA)

Icefaces example hotel search conversation timeouts --------------------------------------------------- Key: JBSEAM-2952 URL: http://jira.jboss.com/jira/browse/JBSEAM-2952 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas I believe that the conversation handling may have a problem. - Search for hotels (note no hotel list by default - inconsistent will other booking examples). - Launch one hotel into a tab (typically using center mouse button) - The new tab contains the same search results, not the hotel from the link. - The links in the new tab table do not do anything. - Must click "more results" to have any other hotel links work. - Begin to book a different hotel in the original tab - At this point you should have 2 conversation/workspaces. - Note attempting to change the workspace using the links at the bottom do no do anything - Eventually you will get a "user session timeout" error. This is not a http session timeout. - I think that something gets confused with the conversations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3318) seambay example throws NullPointerException with message: "Argument Error: Parameter message is null" when bidding

by Jay Balunas (JIRA)

seambay example throws NullPointerException with message: "Argument Error: Parameter message is null" when bidding ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-3318 URL: https://jira.jboss.org/jira/browse/JBSEAM-3318 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Fix For: 2.1.0.BETA2 When attempting to place a bid on any of the items a seam debug page is shown with this error - note it is swallowed by the log and is not shown. Exception during request processing: Caused by java.lang.NullPointerException with message: "Argument Error: Parameter message is null" com.sun.faces.util.Util.notNull(Util.java:241) com.sun.faces.context.FacesContextImpl.addMessage(FacesContextImpl.java:322) org.jboss.seam.faces.FacesMessages.beforeRenderResponse(FacesMessages.java:48) org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:485) org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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:406) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:73) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) java.lang.Thread.run(Thread.java:595) -- 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

17 years, 7 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3332) Support iterators from richfaces extended data model in excel exporter

by Nicklas Karlsson (JIRA)

Support iterators from richfaces extended data model in excel exporter ---------------------------------------------------------------------- Key: JBSEAM-3332 URL: https://jira.jboss.org/jira/browse/JBSEAM-3332 Project: Seam Issue Type: Feature Request Components: Excel Reporter: Nicklas Karlsson Assignee: Daniel Roth Priority: Minor Fix For: 2.1.0.BETA2 Richfaces apparently has some "extended data model". The UIWorkbook.unwrapIterator switch statement should cover this case also (need to debug to see where the iterator really is) -- 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

17 years, 7 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008