November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2267) conversations problem :: sourceId=null

by Tomas Cerny (JIRA)

conversations problem :: sourceId=null -------------------------------------- Key: JBSEAM-2267 URL: http://jira.jboss.com/jira/browse/JBSEAM-2267 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Linux Reporter: Tomas Cerny Priority: Critical Fix For: 2.0.1.GA ref: http://www.icefaces.org/JForum/posts/list/0/6264.page#27733 I have an explicit named conversation. I am starting the conversation on my method @Begin(flushMode=FlushModeType.MANUAL,join=true, pageflow="personHomeFlow",id="person-#{person.username}") I am using pageflow that start by state Everything worked fine until I sticked to my page about 20 UIinputs Then it started to behave completely crazy. Navigation goes well, then I want to call #{manager.save}. It even does not call the method save and log has --------------------------------------------- 20:31:21,692 INFO [lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or was processing another request), detail=(The conversation ended, timed out or was processing another request)] sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or was processing another request), detail=(The conversation ended, timed out or was processing another request)] --------------------------------------------- but conversation is still alive I can go back! my jpdl file --------------------------------------------- <pageflow-definition xmlns="http://jboss.com/products/seam/pageflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.com/products/seam/pageflow http://jboss.com/products/seam/pageflow-2.0.xsd" name="personHomeFlow"> <start-state name="personHomeFlow" > <transition name="success" to="viewPersonHome"/> </start-state> <page name="viewPersonHome" redirect="yes" view-id="/private/people/personHome.xhtml"> <description>View person home: #{person.username}</description> <transition name="success" to="end"></transition> <transition name="cancel" to="end"></transition> </page> <page name="end" redirect="yes" view-id="/private/people/personList.xhtml"> <end-conversation/> <redirect/> </page> </pageflow-definition> --------------------------------------------- pages.xml had --------------------------------------------  ------------------------------------------------ by commenting it out does not work redirect but message has not repeated second line My conversation is still alive ? that is a question I am using richfaces and reRender for my form I cannot send you simple code because I have a million facelet pages. When I use just 5 UIinputs it works?? So problem can also be in JPDL that starts by state. I tried to increase conversation timeout did not help! I tried to use not named conversation and did not help neither! What about redirects? Tomas -- 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 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2272) Workspace description

by Tomas Cerny (JIRA)

Workspace description --------------------- Key: JBSEAM-2272 URL: http://jira.jboss.com/jira/browse/JBSEAM-2272 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Linux Gentoo Reporter: Tomas Cerny Fix For: 2.0.1.GA In your documentation is many various combinations of managing workspace. But it seem like there is not a combination that would allow me to redirect in jPDL and to specify description together. There are examples where I can use pages.xml like this ==================================================== <page view-id="/private/people/personHomeView.xhtml" conversation-required="true" no-conversation-view-id="/private/home.xhtml"> Foo at #{bar.circle} </page> ==================================================== but this is completely ignored when I use pageflow jPDL! other alternative is to use jPDL ==================================================== <page name="viewPersonHomeAjax" timeout="600000" view-id="/private/people/personHomeAjax.xhtml"> <description> View person home: #{person.username} </description> <transition name="cancel" to="end"></transition> </page> ==================================================== but then I cannot use redirect! this fails to deploy: ==================================================== <page name="viewPersonHomeAjax" timeout="600000" view-id="/private/people/personHomeAjax.xhtml"> <redirect/> <description> View person home: #{person.username} </description> <transition name="cancel" to="end"></transition> </page> ==================================================== this is ignored at all (what is the purpose of that???): ==================================================== <page name="viewPersonHomeAjax" timeout="600000" redirect="yes" view-id="/private/people/personHomeAjax.xhtml"> <description> View person home: #{person.username} </description> <transition name="cancel" to="end"></transition> </page> ==================================================== Maybe there is some magic combination but then it is not in documentation Tomas -- 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 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2269) s:defaultAction should support s:link, s:button

by Pete Muir (JIRA)

s:defaultAction should support s:link, s:button ----------------------------------------------- Key: JBSEAM-2269 URL: http://jira.jboss.com/jira/browse/JBSEAM-2269 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.x -- 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 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1893) Default action for a JSF form

by Fernando Montaño (JIRA)

Default action for a JSF form ----------------------------- Key: JBSEAM-1893 URL: http://jira.jboss.com/jira/browse/JBSEAM-1893 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Fernando Montaño Enable the possibility to invoke some action (e.g. commandButton) when the user hits Enter key in a form. -- 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 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2252) <s:conversationPropagation> rename attribute propagation=> type

by Tobias Kilian (JIRA)

<s:conversationPropagation> rename attribute propagation=> type --------------------------------------------------------------- Key: JBSEAM-2252 URL: http://jira.jboss.com/jira/browse/JBSEAM-2252 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.GA Reporter: Tobias Kilian Priority: Minor http://docs.jboss.com/seam/2.0.0.CR2/reference/en/html/controls.html In section <s:conversationPropagation> it is stated, that the attribute controlling the propagation is called 'propagation', while under usage, 'type' is used. I tried both and type is working wheras propagation is not. -- 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 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2262) support wildcard prefix on hibernate.cfg.xml in build script on seam-gen projects

by Dan Allen (JIRA)

support wildcard prefix on hibernate.cfg.xml in build script on seam-gen projects --------------------------------------------------------------------------------- Key: JBSEAM-2262 URL: http://jira.jboss.com/jira/browse/JBSEAM-2262 Project: JBoss Seam Issue Type: Task Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA When jBPM is added to a project, a new hibernate configuration must be setup. Rather than use the default, I prefer to name the configuration jbpm-hibernate.cfg.xml so that its purpose is clear and so it doesn't collide with an existing Hibernate configuration. However, the build script only copies the exact file name hibernate.cfg.xml. The proposed change will simply add a wildcard at the beginning of the included filename on the fileset node. It will not affect existing configurations. -- 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 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2190) SeamScopePostProcessor should include defaultAutoCreate attribute

by Dan Allen (JIRA)

SeamScopePostProcessor should include defaultAutoCreate attribute ----------------------------------------------------------------- Key: JBSEAM-2190 URL: http://jira.jboss.com/jira/browse/JBSEAM-2190 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.CR3 Reporter: Dan Allen Assigned To: Michael Youngstrom Fix For: 2.0.1.GA In terms of the Seam-Spring bridge, the auto-create functionality is almost always desired. The default behavior for Seam-scoped Spring beans is to not register an auto-create variable. As a result, I find that I have to resort to using a nested <seam:component> simply to get auto-create functionality. I can understand that the setting has to be global (whether or not to register an auto-create variable in the SeamScopePostProcessor), but I feel it should at least be a switch that would appear on the <seam:configure-scopes> tag. -- 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 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2228) The isDefined() method in a seam-gen generated EntityHome class incorrectly applies a Strings.isEmpty() method

by Shawn Thomas (JIRA)

The isDefined() method in a seam-gen generated EntityHome class incorrectly applies a Strings.isEmpty() method --------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2228 URL: http://jira.jboss.com/jira/browse/JBSEAM-2228 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Shawn Thomas I attempted to reverse engineer a database with seam-gen/generate-entities. Everything was built correctly. But the isDefined() method in the generated TransectHome class incorrectly applies a Strings.isEmpty() method (the objects are not always Strings). -- 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 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2224) EntityQuery.resultList contains all nulls after AJAX request

by Alex Savitsky (JIRA)

EntityQuery.resultList contains all nulls after AJAX request ------------------------------------------------------------ Key: JBSEAM-2224 URL: http://jira.jboss.com/jira/browse/JBSEAM-2224 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.GA Reporter: Alex Savitsky The resultList of an EntityQuery gets reset to contain all nulls after several AJAX interactions. I'm not sure whether it's Seam or RichFaces that causes the problem (I'm still investigating the cause), but it's bound to be one or the other, because a) it's the EntityQuery that gets reset and b) it only happens when one or more Ajax-enabled RichFaces controls are present on the page. The attached test case uses datascroller & data table, but I was able to observe it with other controls, such as suggestion box. Steps to reproduce: 1. Put all libraries listed in WEB-INF/lib/libs.txt in WEB-INF/lib (essentially Seam 2.0.0 GA, RichFaces 3.1.2 GA, Hibernate EM 3.3.1 GA, Facelets 1.1.14, Sun JSF RI 1.2.05, plus supporting libs). I didn't put them into WAR, as this makes it >10M big. 2. Deploy the WAR and access it at http://hostname/TestCase/index.jsf 3. Activate the data scroller TWICE IN A ROW (important) - e.g., press "next page" twice 4. Check the contents of the dropdown (just to know what's there normally) 5. Select an item in the data table 6. Check the contents of the dropdown. All entries are empty now! -- 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 months

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2259) Document which annotations are inherited in Seam

by Pete Muir (JIRA)

Document which annotations are inherited in Seam ------------------------------------------------ Key: JBSEAM-2259 URL: http://jira.jboss.com/jira/browse/JBSEAM-2259 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Priority: Minor Fix For: 2.0.x -- 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 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007