April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2794) Make Seam EL more extensible and unified

by Michael Youngstrom (JIRA)

Make Seam EL more extensible and unified ---------------------------------------- Key: JBSEAM-2794 URL: http://jira.jboss.com/jira/browse/JBSEAM-2794 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.1.0.BETA2 I'm currently having some trouble dealing with ELResolvers in Seam and JSF. 1. It is not very easy to add ELResolvers to Seam (e.g. SpringELResolver must be put in the end of the resolver chain when it should be one of the first.) 2. When executing outside a FacesRequest you have to use the Seam ELResolver infrastructure which doesn't see any of the JSF ELResolvers 3. It would be nice to have a little more control over the order of ELResolvers since I have run into a few recursive situations as EL can sometimes sneak it's way into situations where EL is used in the SeamELResolver to resolve EL. I believe that all of the above can be solved by: 1. Turn the SeamELResolver into a CompositeELResolver where a Seam Component can manage the included ELResolvers. 2. Add the above single SeamCompositeELResolver to the faces-context.xml. Making it so custom ELResolvers can be managed in a single place in Seam for both Faces and non Faces requests. -- 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

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2857) Make Seam pageflow usable by Wicket pages

by paolo di tommaso (JIRA)

Make Seam pageflow usable by Wicket pages ----------------------------------------- Key: JBSEAM-2857 URL: http://jira.jboss.com/jira/browse/JBSEAM-2857 Project: JBoss Seam Issue Type: Feature Request Components: Wicket Affects Versions: 2.1.0.A1 Reporter: paolo di tommaso Wicket integration in Seam currently does not support Page Flow feature. IIt should be supported. // Paolo -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2655) Support for OpenID

by Shane Bryzak (JIRA)

Support for OpenID ------------------ Key: JBSEAM-2655 URL: http://jira.jboss.com/jira/browse/JBSEAM-2655 Project: JBoss Seam Issue Type: Feature Request Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.1.0.GA Norman pointed this out to me, it would be nice if we could support it. "OpenID eliminates the need for multiple usernames across different websites, simplifying your online experience." They have a few Java implementations available for download on the following page. http://wiki.openid.net/Libraries -- 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

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2933) Seam 2.1-snapshot, gwt1.5m2, array issues

by darren hartford (JIRA)

Seam 2.1-snapshot, gwt1.5m2, array issues ----------------------------------------- Key: JBSEAM-2933 URL: http://jira.jboss.com/jira/browse/JBSEAM-2933 Project: Seam Issue Type: Bug Components: GWT Reporter: darren hartford There are some problems with Arrays of DTO's between seam 2.1-snapshot (4/25/2008) and GWT 1.5m2 remoting/rpc. i.e. SimpleDTO[] getMyDtoArray() It is the non-informative 'IncompatibleRemoteServiceException' error and mentions the application out of date, which it is not. No sample project or test case yet as mentioned in the forum post just identified the source of some problems. -- 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

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2704) Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors

by Siarhei Dudzin (JIRA)

Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2704 URL: http://jira.jboss.com/jira/browse/JBSEAM-2704 Project: JBoss Seam Issue Type: Bug Components: Performance and Scalability Affects Versions: 2.0.1.GA, 2.0.0.GA Environment: Seam 2.0.0, 2.0.1 Reporter: Siarhei Dudzin "Since we don't cache this, a particular backing bean might be called hundreds or thousands of times during rendering of a datatable, if a value binding has to be evaluated for each row. If the backing bean is a Seam component, injection of dependencies will occur for every call, involving potentially thousands of map lookups." There is a discussion thread with a bit more data: http://www.seamframework.org/Community/SeamPerformanceOptimization The issue is also recognized at the seamframework.org site itself: http://www.seamframework.org/Documentation/TuningTheSeamWebsite#H-Iterati... Since the issue it known, this JIRA report is created for better traceability. -- 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

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2562) 'Transaction failed' JSF message when number of restriction in EntityQuery changes

by Siarhei Dudzin (JIRA)

'Transaction failed' JSF message when number of restriction in EntityQuery changes ---------------------------------------------------------------------------------- Key: JBSEAM-2562 URL: http://jira.jboss.com/jira/browse/JBSEAM-2562 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.1.GA Environment: JBoss AS 4.2.2, Windows XP Reporter: Siarhei Dudzin When getRestrictions() from EntityQuerry returns dynamic list with restrictions a JSF error message 'Transaction failed' is shown (no exceptions just a message). I noticed this happens when the size of the list is decreased in comparison with the previous request (There is also a warning in the logs). While this JSF message is shown the query still works! After some debugging I've found that the underlying error is that a value binding could not be found. A temprorarily workaround is to keep the restriction list constant by filling the 'gaps' with placeholders like #{true}=true (just to keep the size constant). -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2881) Conversation Switcher doesn't work with natural conversations

by Caleb Land (JIRA)

Conversation Switcher doesn't work with natural conversations ------------------------------------------------------------- Key: JBSEAM-2881 URL: http://jira.jboss.com/jira/browse/JBSEAM-2881 Project: Seam Issue Type: Bug Components: JSF Controls, JSF Integration Affects Versions: 2.0.2.CR1 Environment: Seam 2.0.2.CR1, Mac OS X 10.5, Java 1.5.0_13 Reporter: Caleb Land The Switcher component's (org.jboss.seam.faces.Switcher) switch() method does not work correctly when using natural conversations. The issue is related to line 102 (in trunk and in 2.0.2.CR1) where seam tests whether the selected item is an outcome or a conversation id: boolean isOutcome = conversationIdOrOutcome==null || !Character.isDigit( conversationIdOrOutcome.charAt(0) ); The problem is that with natural conversations, the value of conversationIdOrOutcome is something like "accountEdit:4" so the switcher thinks it's a view. I copied the code from the Switcher and created a new component and replaced that line with: boolean isOutcome = conversationIdOrOutcome==null || (!Character.isDigit(conversationIdOrOutcome.charAt(0)) && conversationIdOrOutcome.indexOf(':') < 0); and it works correctly. Of course this approach is naive, but it seems to work for me. -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2154) Only one event fired, even if multiple are specified in pages.xml

by Adam Warski (JIRA)

Only one event fired, even if multiple are specified in pages.xml ----------------------------------------------------------------- Key: JBSEAM-2154 URL: http://jira.jboss.com/jira/browse/JBSEAM-2154 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Adam Warski If I have: <page ...> <navigation ...> <raise-event type="event1" /> <raise-event type="event2" /> </navigation> </page> or even <page ...> <raise-event type="event1" /> <raise-event type="event2" /> </page> Only the first even is fired (and handled). The second is ignored. -- 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

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2310) Need an option to remove URL parameters from a URL

by Terry (JIRA)

Need an option to remove URL parameters from a URL -------------------------------------------------- Key: JBSEAM-2310 URL: http://jira.jboss.com/jira/browse/JBSEAM-2310 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: All environments Reporter: Terry Priority: Minor When JSF page is loaded, seam goes through all the page links and instantiate seam components referenced in those pages, it then adds url parameters (specified in page.xml file) to those links. Both of these features should be option: auto Instantiation of seam components referenced in jsf pages and appending parameters to the link on jsf page. I have menu with about 40 links to jsf pages: everytime my page refreshes all the seam components in those 40+ pages get instantiated and all think get appened with parameters specified in page.xml files. -- 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

6
10
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2008