May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1180) Hibernate & JPA examples still using myfaces

by Pete Muir (JIRA)

Hibernate & JPA examples still using myfaces -------------------------------------------- Key: JBSEAM-1180 URL: http://jira.jboss.com/jira/browse/JBSEAM-1180 Project: JBoss Seam Issue Type: Bug Components: Examples Reporter: Pete Muir -- 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

18 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1329) Fileupload contentLength > maxRequestSize throws RuntimeException

by Kenneth Christensen (JIRA)

Fileupload contentLength > maxRequestSize throws RuntimeException ----------------------------------------------------------------- Key: JBSEAM-1329 URL: http://jira.jboss.com/jira/browse/JBSEAM-1329 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Kenneth Christensen Priority: Minor Because it's a RuntimeException I can't tell the user about the problem, e.g. file is too big. I can only show the user a standard error page :-( What about a MaxRequestSizeException? If I have a MaxRequestSizeException I can show the user a non-standard error page. e.g. Code: <pages> <exception class="org.jboss.seam.MaxRequestSizeException"> <redirect view-id="/uploadError.xhtml"> <message>File is too big</message> </redirect> </exception> </pages> Will it be possible to implement above feature in the fileupload component? -- 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

18 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1020) Configurable Drools event listeners (primarily for debug logging)

by Christian Bauer (JIRA)

Configurable Drools event listeners (primarily for debug logging) ----------------------------------------------------------------- Key: JBSEAM-1020 URL: http://jira.jboss.com/jira/browse/JBSEAM-1020 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak Priority: Minor I want to see what is going on when my rules are evaluated, according to the Drools docs this is how: workingMemory.addEventListener( new DebugWorkingMemoryEventListener() ); I have to do that in code right now, would be nice to be able to configure the identity component externally in config file. It also doesn't work, at least not in JBoss with a WAR deployment. I don't see any debug printed on System.out. Task: Ask the drools guys how we get logging for Seam users. -- 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

18 years, 10 months

5
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-449) Get CRUD messages out of components.xml and into resource bundles

by Gavin King (JIRA)

Get CRUD messages out of components.xml and into resource bundles ----------------------------------------------------------------- Key: JBSEAM-449 URL: http://jira.jboss.com/jira/browse/JBSEAM-449 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.BETA2 update/delete/create messages don't belong in components.xml -- 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

18 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1164) s:selectDate should trigger onchange if destination object has onchange handler defined.

by Chris Sweeney (JIRA)

s:selectDate should trigger onchange if destination object has onchange handler defined. ---------------------------------------------------------------------------------------- Key: JBSEAM-1164 URL: http://jira.jboss.com/jira/browse/JBSEAM-1164 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Sweeney in /org/jboss/seam/ui/resource/date/calendar.js function __clickCalendar(calName, year, month, day) { getObject(calName).value = __calendarFactory.formatDate(year, month + 1, day); //change follows if(getObject(calName).onchange){ getObject(calName).onchange(); } //change_end } Tested with -Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 -Microsoft Internet Explorer 5.2 for Mac -Safari, Version 2.0.4 (419.3) -- 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

18 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-642) Improve seam-gen generated look and feel

by Ronald van Kuijk (JIRA)

Improve seam-gen generated look and feel ---------------------------------------- Key: JBSEAM-642 URL: http://jira.jboss.com/jira/browse/JBSEAM-642 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 1.1.0.GA Environment: N/A Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk Priority: Minor Fix For: 1.2.0.BETA1 The look and feel of the pages generated by seam-gen should have a more professional look and feel. Things to do: - show/hide optional elements - mark required elements as such - font types - colors - menu - breadcrums - footer - validation errors / message -- 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

18 years, 11 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1299) s:link - Postback before redirect triggers Page Action of PREVIOUS page

by John Chesher (JIRA)

s:link - Postback before redirect triggers Page Action of PREVIOUS page ------------------------------------------------------------------------- Key: JBSEAM-1299 URL: http://jira.jboss.com/jira/browse/JBSEAM-1299 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Environment: Seam 1.2-Patch1 Reporter: John Chesher Scenario: Page A contains an <s:link> to go to page B. Page A has a page action defined in pages.xml. When I click the s:link on Page A, to go to Page B, it invokes the page action for Page A before redirecting to Page B. If I replace the s:link with an h:commandLink, it works as I would expect it to, i.e., no page action for Page A. I have now retested and I have this scenario in multiple instances within my application. In most cases, I didn't even realize that it was invoking the page action for Page A, as by luck the method was designed such that it did not throw an exception or cause any other noticeable problems. However, I finally noticed this behavior when my luck ran out and I wrote a page action method that threw an exception when called unitentionally in this situation. Is this perhaps a bug in s:link or am I not properly understanding and utilizing its capabilities? -- 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

18 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1308) UnifiedELValueBinding needs default constructor so that it is properly Serailizable

by Chris Rudd (JIRA)

UnifiedELValueBinding needs default constructor so that it is properly Serailizable ----------------------------------------------------------------------------------- Key: JBSEAM-1308 URL: http://jira.jboss.com/jira/browse/JBSEAM-1308 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Reporter: Chris Rudd UnifiedELValueBinding cannot be restored properly when referenced by a component 09:51:46,256 ERROR [ExceptionFilter] exception root cause java.lang.RuntimeException: Could not restore StateHolder of type org.jboss.seam.util.UnifiedELValueBinding (missing no-args constructor?) at javax.faces.component.UIComponentBase.restoreAttachedState(UIComponentBase.java:894) at javax.faces.component.UIComponentBase.restoreValueBindingMap(UIComponentBase.java:1009) at javax.faces.component.UIComponentBase.restoreState(UIComponentBase.java:951) at javax.faces.component.UICommand.restoreState(UICommand.java:189) at org.ajax4jsf.ajax.html.HtmlAjaxCommandButton.restoreState(HtmlAjaxCommandButton.java:1379) at javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:728) at javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:719) at javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:719) at org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreComponentState(JspStateManagerImpl.java:221) at org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreView(JspStateManagerImpl.java:287) at org.ajax4jsf.framework.ajax.AjaxStateManager.restoreView(AjaxStateManager.java:83) at org.jboss.seam.jsf.SeamStateManager.restoreView(SeamStateManager.java:49) at org.ajax4jsf.framework.ajax.AjaxStateManager.restoreView(AjaxStateManager.java:83) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.restoreView(JspViewHandlerImpl.java:255) at com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:317) at org.ajax4jsf.framework.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:116) at org.ajax4jsf.framework.ajax.AjaxViewHandler.restoreView(AjaxViewHandler.java:147) at org.jboss.seam.jsf.SeamViewHandler.restoreView(SeamViewHandler.java:64) at com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:317) at org.ajax4jsf.framework.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:116) at org.ajax4jsf.framework.ajax.AjaxViewHandler.restoreView(AjaxViewHandler.java:147) at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:141) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) -- 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

18 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1313) Go back to previous page

by H T (JIRA)

Go back to previous page ------------------------ Key: JBSEAM-1313 URL: http://jira.jboss.com/jira/browse/JBSEAM-1313 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.3.0.BETA1 Reporter: H T Assume there are two pages, p1 and p2. When entering p1, a conversation c1 is started. p1 contains a link to p2 which when clicked will start a nested conversation c2. Feature request: what I would like to see is an extension to s:link/s:button that can be used in p2 that allow it to go back to the previous page p1 and ending the conversation c2. This feature is useful for breadcrumbs and "cancel" buttons but c2 must be a nested conversation. -- 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

18 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1317) ConverterChain constructor does not create a default converter when attached to a value of type String

by Matt Drees (JIRA)

ConverterChain constructor does not create a default converter when attached to a value of type String ------------------------------------------------------------------------------------------------------ Key: JBSEAM-1317 URL: http://jira.jboss.com/jira/browse/JBSEAM-1317 Project: JBoss Seam Issue Type: Bug Components: JSF Environment: CVS Head (May 8 2007) Reporter: Matt Drees from forum post: "...the ConverterChain constructor tries to create a default converter based on the type of the value, but this doesn't work for Strings (debugging showed that facesContext.getApplication().createConverter(String.class) returns null). " -- 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

18 years, 11 months

3
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 May 2007