July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-633) remoting extension in handling exceptions on client side

by Nico Gau (JIRA)

remoting extension in handling exceptions on client side -------------------------------------------------------- Key: JBSEAM-633 URL: http://jira.jboss.com/jira/browse/JBSEAM-633 Project: JBoss Seam Issue Type: Patch Components: Remoting Affects Versions: 1.1.0.GA Reporter: Nico Gau Priority: Optional Hi all, I don't really know what JIRA is by the way, so hopefully nobody is upset by this post. I first mailed Gavin but he told me I should put it in JIRA. I currently work on a project which uses Seam Remoting directly and I didn't find a neat way in handling errors on the client side as Exceptions are not propagated to it. Therefore I changed Seam to transmit all exceptions which can be handled in the javascript part via another callback. E.g.: Seam.Component.getInstance('userManager').currentUser(function(user) { alert("user: " + user); }, function(ex) { alert("exception occured: " + ex.getMessage()); }); As the exception handler is optional, the change would not brake any client code. If you are interested in the change, you can reach me at heinzbeinz AT googlemail.com -- 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, 2 months

7
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1179) dvd store: Function 's:hasRole' not found

by Pete Muir (JIRA)

dvd store: Function 's:hasRole' not found ----------------------------------------- Key: JBSEAM-1179 URL: http://jira.jboss.com/jira/browse/JBSEAM-1179 Project: JBoss Seam Issue Type: Bug Components: Examples, Security Reporter: Pete Muir Replicate by logging in as manager and attempting to change the order process 10:32:34,117 ERROR [STDERR] java.lang.ClassNotFoundException: org.jboss.seam.security.SecurityFunctions 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source) 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;I)Ljava.lang.Class;(Unknown Source) 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl$Function.getMethod(FunctionMapperImpl.java:147) 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl.resolveFunction(FunctionMapperImpl.java:53) 10:32:34,117 ERROR [STDERR] at org.apache.el.parser.AstFunction.getValue(AstFunction.java:71) 10:32:34,117 ERROR [STDERR] at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) 10:32:34,117 ERROR [STDERR] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:384) 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) 10:32:34,117 ERROR [STDERR] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:32:34,117 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:32:34,117 WARN [lifecycle] javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found javax.faces.FacesException: javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:387) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) 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:228) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) -- 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, 2 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1242) Entity converter for managed Hibernate sessions

by Patrick Ruhkopf (JIRA)

Entity converter for managed Hibernate sessions ----------------------------------------------- Key: JBSEAM-1242 URL: http://jira.jboss.com/jira/browse/JBSEAM-1242 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Patrick Ruhkopf Priority: Minor The EntityConverter (<s:convertEntity>) only works with an EntityManager but not with Hibernate managed sessions. Please find attached a HibernateEntityConverter for 1.2.1 GA. I didn't supply a patch yet, because, as petemuir pointed out, the current HEAD contains a lot of refactoring. -- 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, 2 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1350) Provide download component (e.g.<s:download value=#{FileManager.getFileById('10')" contentType="#{FileManager.contentType}" />)

by jarkko Lietolahti (JIRA)

Provide download component (e.g.<s:download value=#{FileManager.getFileById('10')" contentType="#{FileManager.contentType}" />) ------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1350 URL: http://jira.jboss.com/jira/browse/JBSEAM-1350 Project: JBoss Seam Issue Type: Feature Request Reporter: jarkko Lietolahti <s:download value=#{FileManager.getFileById('10')" contentType="#{FileManager.contentType}" /> We're going to create new (more general component) which allows the user to download a file (any resource, Excel file, Document whatever). The plan is to create a new UI component named UIDownload which has attributes like value, contentType (some more?). 1) UIDownload a backing bean (value) (is this still valid word in the seam world?) to generate the data ( allow byte[], OutputStreams ?). 2) UIDownload creates DownloadResource which is stored in DownloadStore. 3) UIDownload generates HTML which redirects the browser to ResourceServlet 4) ResourceServlet then uses DownloadResource to get hold of the data and the pushes it to browser The reason for this is that we're building portlets with Seam and it's impossible to "download" files from a portal environment without additional servlet and we think it's good idea to reuse existing stuff. Patch coming soon (if we can make it work ;) -- 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, 3 months

5
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1536) Change field naming in seam-gen generated app

by Mikhail Grushinskiy (JIRA)

Change field naming in seam-gen generated app --------------------------------------------- Key: JBSEAM-1536 URL: http://jira.jboss.com/jira/browse/JBSEAM-1536 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy Seam-Gen names it after object property name. Every time cache of the letter switches from lower to upper seam-gen could insert space so 'clientAddress' will be 'Client Address' (note: space between words) in generated xhtml input field labels and table headers. (Or even better put into messages.properties so localization of the app becomes easier) -- 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, 4 months

6
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-681) PDF form support

by Norman Richards (JIRA)

PDF form support ---------------- Key: JBSEAM-681 URL: http://jira.jboss.com/jira/browse/JBSEAM-681 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards Assigned To: Norman Richards I'd like to be able to support PDF forms. We would like to support: 1) Generation of PDFs with forms 2) postback (FDF and/or HTML) to the server 3) Using forms as a server-side templating mechanism -- 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, 5 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-903) @Bidirectional to combine @In and @Out

by Andrew (JIRA)

@Bidirectional to combine @In and @Out -------------------------------------- Key: JBSEAM-903 URL: http://jira.jboss.com/jira/browse/JBSEAM-903 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Andrew Priority: Minor IMO, it would be great to have an InOut annotation that can combine In and Out to avoid excessive typing. Examples: Now: @In(required=false, value="someString", scope=ScopeType.EVENT) @Out(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; Easier as: @Bidirectional(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; -- 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, 6 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1508) Decouple framework from JSF

by Gavin King (JIRA)

Decouple framework from JSF --------------------------- Key: JBSEAM-1508 URL: http://jira.jboss.com/jira/browse/JBSEAM-1508 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.BETA2 We have dependencies there that we don't really need. -- 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, 6 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-541) ConversationEntry reports the wrong description

by Norman Richards (JIRA)

ConversationEntry reports the wrong description ----------------------------------------------- Key: JBSEAM-541 URL: http://jira.jboss.com/jira/browse/JBSEAM-541 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Norman Richards Assigned To: Gavin King The linked forum post shows one example of this bug, though it is not directly the issue the poster is complaining of. Using the forum application as a guide, start a conversation and then start a nested conversation. End the nested conversation. The description of the parent conversation in the converstion list on will be incorrect. (it will have the name of the current conversation that just ended) This happens because of the following code: public String getDescription() { if ( isCurrent() ) { String desc = Conversation.instance().description; if (desc!=null) return desc; } return description; } public boolean isCurrent() { Manager manager = Manager.instance(); if ( manager.isLongRunningConversation() ) { return id.equals( manager.getCurrentConversationId() ); } else if ( manager.isNestedConversation() ) { return id.equals( manager.getParentConversationId() ); } else { return false; } } The parent conversation entry is considered "current". (isLongRunning() is false and isNestedConversation() is true) Because of this, the ConversationEntry description is ignored in favor of Conversation.instance().description. (Again, Conversation.instance(), is the nested conversation that just ended) Subsequent requests display the conversation description correctly since they are done in the context of the correct conversation. The isNestedConversation() check looks to be the source of the problem. I can't figure out what case that would make sense for. -- 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, 6 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1262) Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes)

by Nathaniel Stoddard (JIRA)

Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes) ------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1262 URL: http://jira.jboss.com/jira/browse/JBSEAM-1262 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard Currently, each validation specified a single message resource to be used as the error message. It would be helpful if there was some way to customize the error messages to be used such that in one case "Contact address is required." is displayed, while in others "Billing address is required", for example. Annotating model classes with validation rules limits the reuse of those classes since the validation messages offer limited flexibility. Since validated fields in the domain classes aren't necessarily associated with a UIInput on a page, it would be helpful to have more flexible annotations, such as: @MaxLength(messages = {@Message(role='contactForm', value='contact.too_long'), @Message(role='billingForm', value='billing.too_long')}) private String field; Also needed would be some way of indicated to the UIView which 'role' should be used when validation takes place. -- 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, 6 months

3
6
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 July 2007