July 2008 - seam-issues - Jboss List Archives

[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

15 years, 11 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

15 years, 11 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

15 years, 11 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3033) make s:graphicImage work with s:cache

by Daniel Roth (JIRA)

make s:graphicImage work with s:cache -------------------------------------- Key: JBSEAM-3033 URL: http://jira.jboss.com/jira/browse/JBSEAM-3033 Project: Seam Issue Type: Feature Request Components: JSF Controls, Performance and Scalability Affects Versions: 2.0.2.GA Environment: All Reporter: Daniel Roth Priority: Minor Fix For: The future s:graphicImage with its transformations is a great tag to use for user uploaded images. However, having a couple of images on the same page makes the page a bit slow to load due to transformations. One can quite easy make the transformations oneself and cache them, however a nicer solution would be if s:graphicImage could be used inside s:cache tags. -- 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-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

15 years, 11 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

15 years, 11 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

15 years, 11 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2961) Because of seam-gen lib changes hsqldb.jar is not where it used to be - search for reference that might need changes

by Jay Balunas (JIRA)

Because of seam-gen lib changes hsqldb.jar is not where it used to be - search for reference that might need changes -------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2961 URL: http://jira.jboss.com/jira/browse/JBSEAM-2961 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor There was some places that referred to the hsqldb.jar in the seam-gen/lib directory. Search svn for references and just verify that the calls or references are still correct. Most likely would be in the reference docs, or in seam-gen. -- 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-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

15 years, 12 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

15 years, 12 months

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