July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2463) add legendOutlinePaint to line and bar chart

by Dan Allen (JIRA)

add legendOutlinePaint to line and bar chart -------------------------------------------- Key: JBSEAM-2463 URL: http://jira.jboss.com/jira/browse/JBSEAM-2463 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA You can adjust every other line on used on the line and bar charts except for the one that surrounds the legend. This patch adds a new attribute that controls the color used. If left off, the line around the legend will be black. Unfortunately, since piechart does not extend from the same hierarchy, more work will need to be done to be able to control the legend on that type of chart. For now, I am deferring that request. -- 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

15 years, 11 months

3
6
0 / 0

[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

15 years, 11 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3148) Seam URL encoding UTF-8 conflicts with Tomcat Default ISO-8859-1

by Michael Youngstrom (JIRA)

Seam URL encoding UTF-8 conflicts with Tomcat Default ISO-8859-1 ---------------------------------------------------------------- Key: JBSEAM-3148 URL: http://jira.jboss.com/jira/browse/JBSEAM-3148 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.3.GA I am having trouble transmitting multi-byte characters through page params. The problem appears to be this: 1. The servlet spec defaults URI decoding as ISO-8859-1. 2. Calling request.setCharacterEncoding() changes this default for the body of the message (post params) 3. In Tomcat calling request.setCharacterEncoding() does not change the encoding tomcat uses to decode the url. In order to change the uri encoding the useBodyEncodingForURI=true must be set in tomcat configuration (http://tomcat.apache.org/tomcat-5.5-doc/config/http.html). 4. A seam redirect uses seam.core.Manager.encode() to encode request params which encodes the parameters using UTF-8. 5. So when a multi-byte character is communicated as a page param by default it gets encoded by Seam in UTF-8 and decoded by Tomcat using ISO-8859-1. How do we fix this? Two options: 1. Change Manager.encode() to use ISO-8859-1 instead of UTF-8 by default. 2. Make everyone who uses tomcat set useBodyEncodingForURI=true in their configuration. I don't know if tomcat is the only container that doesn't by default URIDecode using the same content type as request.setCharacterEncoding(). I'm leaning towards option #1. Thoughts? Mike -- 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

15 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3195) Support for @Observer in Wicket classes

by Pete Muir (JIRA)

Support for @Observer in Wicket classes --------------------------------------- Key: JBSEAM-3195 URL: https://jira.jboss.org/jira/browse/JBSEAM-3195 Project: Seam Issue Type: Feature Request Components: Wicket Reporter: Pete Muir Don't know if this is good or not -- 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

15 years, 11 months

2
2
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

15 years, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3194) BPM control in Wicket classes

by Pete Muir (JIRA)

BPM control in Wicket classes ----------------------------- Key: JBSEAM-3194 URL: https://jira.jboss.org/jira/browse/JBSEAM-3194 Project: Seam Issue Type: Feature Request Components: Wicket Reporter: Pete Muir Assignee: Pete Muir Fix For: 2.1.0.BETA1 -- 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

15 years, 11 months

2
1
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

15 years, 12 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3182) Support hot redeployment of Seam enabled Wicket components

by Pete Muir (JIRA)

Support hot redeployment of Seam enabled Wicket components ---------------------------------------------------------- Key: JBSEAM-3182 URL: https://jira.jboss.org/jira/browse/JBSEAM-3182 Project: Seam Issue Type: Feature Request Components: Wicket Reporter: Pete Muir -- 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

15 years, 12 months

2
1
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

16 years

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

16 years

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008