February 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

16 years, 2 months

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

16 years, 2 months

3
8
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

16 years, 2 months

3
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

16 years, 2 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

16 years, 3 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

16 years, 3 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2402) Validate that @Converter and @Validator components are declared @BypassInterceptors

by Pete Muir (JIRA)

Validate that @Converter and @Validator components are declared @BypassInterceptors ----------------------------------------------------------------------------------- Key: JBSEAM-2402 URL: http://jira.jboss.com/jira/browse/JBSEAM-2402 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Fix For: 2.0.1.GA -- 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, 3 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2471) add s:concat and s:range functions

by Dan Allen (JIRA)

add s:concat and s:range functions ---------------------------------- Key: JBSEAM-2471 URL: http://jira.jboss.com/jira/browse/JBSEAM-2471 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.x Attachments: JBSEAM-2471-v1.txt My #1 EL pet peeve is that there is no way to concatenate a string. This is like serious basic stuff and it is perfectly reasonable to want to perform this task in EL. I realize I could invent my own solution (and I have), but we want to sweep those common cases under the rug like what was done with the magic collection functions (size, isEmpty, etc). How about s:concat('one', 'two')? I am going to squeeze one more in here. I can't tell you the number of times I have needed to quickly create an iteration loop in the UI over a range of numbers, only to realize that there isn't an easy way aside from creating a component. Can we add an s:range() function that creates a collection on the fly? s:range(1, 5) This is somewhat of a precedence since the only two functions in s: right now are security related. -- 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, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2094) Improve documentation of nested conversations

by Pete Muir (JIRA)

Improve documentation of nested conversations --------------------------------------------- Key: JBSEAM-2094 URL: http://jira.jboss.com/jira/browse/JBSEAM-2094 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Fix For: 2.0.2.GA There have been some good discussions of nested conversations on the forum recently, I think we can take some of this into the reference manual -- 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, 3 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1982) Improved documentation for Nested Conversations

by Jacob Orshalick (JIRA)

Improved documentation for Nested Conversations ----------------------------------------------- Key: JBSEAM-1982 URL: http://jira.jboss.com/jira/browse/JBSEAM-1982 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick Nested conversations have been discussed at length on several occasions on the forum. The documentation states: "A conversation may be thought of as a continuable state. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus insuring truly correct behavior in the face of backbuttoning and workspace management." This gives the impression of use of nested conversations to achieve a continuation server approach. This approach is possible and is described at the forum reference, but it seems that most developers use nested conversations for sub-flows ending the conversation at the end of the sub-flow. This does not allow back-buttoning to the sub-flow (which seems to be in conflict with the documentation above). (I will add a link to an article describing the continuation approach in a few weeks, perhaps it could serve as a patch) -- 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, 3 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008