November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2854) Provide a way to nest pageflows

by Marcell Barbacena (JIRA)

Provide a way to nest pageflows ------------------------------- Key: JBSEAM-2854 URL: http://jira.jboss.com/jira/browse/JBSEAM-2854 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Core, JSF Controls Affects Versions: 2.0.1.GA Environment: All Reporter: Marcell Barbacena The current behaviour of pageflow subprocess tag is to include the pageflow definition in the the current flow, meaning that the parent pageflow is paused until the included pageflow ends. However, sometimes it is desired that the parent pageflow do not "pause" and that the included gain its own flow. The semantics of this nested pageflow is: - when starts: provided a nested conversation from the parent pageflow. - when ends: go back do the state before the nesting. If the parent pageflow is not associated in any way to the nested, its flow goes without interfering with the nested. E.g.: Parent directed graph: startpage1->page1; page1->page2; page1->nested; nested->page2; page2->page3; page3->endpage1; Nested graph: startpage2->page5; page5->page6; page6->endpage2 Then we can have: parent: startpage1->page1; parent: page1->nested; nested: startpage2->page5; nested: page5->page6; parent: page1->page2; parent: page2>page3; nested: page6->endpage2 nested:endpage2->page2; parent: page3->endpage1; nested: page2>page3; nested: page3->endpage1; See that the nested pageflow gains his own flow, i.e. independent of the parent. -- 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, 10 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2940) upgrade to Hibernate 3.2.5

by Dan Allen (JIRA)

upgrade to Hibernate 3.2.5 -------------------------- Key: JBSEAM-2940 URL: http://jira.jboss.com/jira/browse/JBSEAM-2940 Project: Seam Issue Type: Task Affects Versions: 2.1.0.A1 Reporter: Dan Allen Assigned To: Pete Muir Priority: Minor Fix For: 2.1.0.GA Hibernate in JBoss AS 4.2.2.GA is 4.2.1.sp1. However, it is not the same JAR as what is in the JBoss Maven 2 repository. The JAR from the Maven 2 repository is a different build. It is missing the specialized Oracle dialects (8i, 9i, and 10g). That appears to be the only files that are missing, however it could be that some files differ as well. And according to this, the Hibernate in JBoss AS 4.2.2.GA is 3.2.0.GA! http://fisheye.jboss.org/browse/JBossAS/tags/JBoss_4_2_2_GA/build/build-t... We just need to upgrade to get to a clean build ;) -- 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, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2746) Empty first search result page if (hits % pagesize == 0)?

by Nicklas Karlsson (JIRA)

Empty first search result page if (hits % pagesize == 0)? ---------------------------------------------------------- Key: JBSEAM-2746 URL: http://jira.jboss.com/jira/browse/JBSEAM-2746 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Nicklas Karlsson Assigned To: Christian Bauer I searched for "production" and got "1 to 15 of 60 hit(s)" but an empty list. Off by one pagination if hits mod results is 0? -- 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, 10 months

5
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1587) page parameters: option to bypass model-based validations

by Hung Tang (JIRA)

page parameters: option to bypass model-based validations --------------------------------------------------------- Key: JBSEAM-1587 URL: http://jira.jboss.com/jira/browse/JBSEAM-1587 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Hung Tang -- 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, 10 months

7
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3767) Italian translation of Seam manual

by Nicola Benaglia (JIRA)

Italian translation of Seam manual ---------------------------------- Key: JBSEAM-3767 URL: https://jira.jboss.org/jira/browse/JBSEAM-3767 Project: Seam Issue Type: Release Reporter: Nicola Benaglia Priority: Optional This Jira Issue is for coordinating the actity of translation of Seam manual in italian. -- 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

16 years, 10 months

4
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3698) Error during rendering of an EMail in an event listener causes failure in rendering of next page

by Wayne Bagguley (JIRA)

Error during rendering of an EMail in an event listener causes failure in rendering of next page ------------------------------------------------------------------------------------------------ Key: JBSEAM-3698 URL: https://jira.jboss.org/jira/browse/JBSEAM-3698 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Windows XP, Java 6, 2GB RAM, JBoss 4.2.2.GA Reporter: Wayne Bagguley Assignee: Pete Muir I have a method that is defined as a listener like this : @Observer(JpaIdentityStore.EVENT_USER_CREATED) This attempts to send an email to the user when he registers but if the email rendering fails for some reason the exception is caught and the method returns normally. However, instead of the next page being rendered, the original page gets rendered incorrectly, with parts of the form in the wrong place. The failure of rendering the EMail should not affect the progress of the rendering of the next page if the exception is caught. -- 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

16 years, 10 months

8
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam

by Florian Keusch (JIRA)

JPDL navigation and seam ------------------------ Key: JBSEAM-3056 URL: http://jira.jboss.com/jira/browse/JBSEAM-3056 Project: Seam Issue Type: Task Components: BPM Reporter: Florian Keusch hi In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem: if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown. This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira. It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown: //now check that the restored view id matches what we expect //from the pageflow node //TODO: we need some way to disable this check, since users // might want some adhoc nav in and out of a pageflow? String viewId = Pages.getViewId(facesContext); if ( !viewId.equals( getPage().getViewId() ) ) { illegalNavigationError(); } If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended. fke -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3699) Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes

by Pete Muir (JIRA)

Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes ---------------------------------------------------------------------------------------------------- Key: JBSEAM-3699 URL: https://jira.jboss.org/jira/browse/JBSEAM-3699 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Priority: Blocker Fix For: 2.1.1.CR1 -- 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

16 years, 10 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2232) Reduce debug log level for events

by Christian Bauer (JIRA)

Reduce debug log level for events --------------------------------- Key: JBSEAM-2232 URL: http://jira.jboss.com/jira/browse/JBSEAM-2232 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Critical Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for org.jboss.seam.Component, you get thousands of these: 12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events. -- 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, 10 months

9
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2690) Websphere on Windows JPA reference guide example throws a ClassCastException

by Jay Balunas (JIRA)

Websphere on Windows JPA reference guide example throws a ClassCastException ---------------------------------------------------------------------------- Key: JBSEAM-2690 URL: http://jira.jboss.com/jira/browse/JBSEAM-2690 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Environment: Webspher 6.1 on Windows Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Several users have reported that on windows following the reference guide JPA example results in a ClassCastException. The issue you are seeing "java.lang.ClassCastException: org.jboss.seam.persistence.EntityManagerFactory incompatible with javax.persistence.EntityManagerFactory:" Following the forum link a user suggests a solution to the issue on windows. Need to verify websphere windows error, and test user fix. Then update document as needed. -- 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, 10 months

6
12
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 November 2008