November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-413) Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-413?page=all ] Norman Richards resolved JBSEAM-413. ------------------------------------ Resolution: Done I made this change. Do we want to update the DTD? If we start adding ANY to the DTD, the DTD will start becoming less useful to users. Perhaps the DTD should only be used for the stricter structure and not for the more freeform structure? > Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml > ------------------------------------------------------------------------------------------- > > Key: JBSEAM-413 > URL: http://jira.jboss.com/jira/browse/JBSEAM-413 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-430) Undeprecate @IfInvalid

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-430?page=comments#action_12346755 ] Gavin King commented on JBSEAM-430: ----------------------------------- Huh? Just put the button outside of the <h:form/> with the validation, if you don't want validation to fire. > Undeprecate @IfInvalid > ---------------------- > > Key: JBSEAM-430 > URL: http://jira.jboss.com/jira/browse/JBSEAM-430 > Project: JBoss Seam > Issue Type: Task > Components: Core > Reporter: Christian Bauer > Priority: Blocker > Fix For: 1.1.0.BETA1 > > > We need @IfInvalid to defer validation until the Invoke Application phase. You can't have a "Previous Page" button in a wizard conversation without it, <s:validateAll> would try to validate the input even if the user clicks "Previous Page". Input validation has to be delayed until "Next Page" is clicked, this is then mapped to a nextPage() action that has an @IfInvalid. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-430) Undeprecate @IfInvalid

by Tony Herstell (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-430?page=comments#action_12346751 ] Tony Herstell commented on JBSEAM-430: -------------------------------------- Add a comand button attribute that allows you to avoid validation e.g. validation="false" or worse use the Value of "Cancel" or "Back" to avoid validation. The ability to go backwards when going through ANY wizard is rather important.. you can even go [Back} on the JBoss installer. Or am I missing the point... > Undeprecate @IfInvalid > ---------------------- > > Key: JBSEAM-430 > URL: http://jira.jboss.com/jira/browse/JBSEAM-430 > Project: JBoss Seam > Issue Type: Task > Components: Core > Reporter: Christian Bauer > Priority: Blocker > Fix For: 1.1.0.BETA1 > > > We need @IfInvalid to defer validation until the Invoke Application phase. You can't have a "Previous Page" button in a wizard conversation without it, <s:validateAll> would try to validate the input even if the user clicks "Previous Page". Input validation has to be delayed until "Next Page" is clicked, this is then mapped to a nextPage() action that has an @IfInvalid. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-413) Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml

by adsf adsf (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-413?page=comments#action_12346733 ] adsf adsf commented on JBSEAM-413: ---------------------------------- I would prefer: <property name="foo" value="theValue" /> Less verbos than the <property>...</property> thing and more readable than the <foo>...</foo> thing. > Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml > ------------------------------------------------------------------------------------------- > > Key: JBSEAM-413 > URL: http://jira.jboss.com/jira/browse/JBSEAM-413 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-167) Nested conversation and pageflow.

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-167?page=all ] Gavin King updated JBSEAM-167: ------------------------------ Fix Version/s: 1.1.0.CR1 > Nested conversation and pageflow. > --------------------------------- > > Key: JBSEAM-167 > URL: http://jira.jboss.com/jira/browse/JBSEAM-167 > Project: JBoss Seam > Issue Type: Bug > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.CR1 > > > We need to clearly define and implement the behavior of pageflows for nested conversations. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-490) <begin-conversation> and <end-conversation> for pages.xml

by Gavin King (JIRA)

<begin-conversation> and <end-conversation> for pages.xml --------------------------------------------------------- Key: JBSEAM-490 URL: http://jira.jboss.com/jira/browse/JBSEAM-490 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 Its very useful to be able to begin and end conversations when we hit a page. -- 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

18 years, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-391) <end-conversation /> ends task

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-391?page=all ] Gavin King closed JBSEAM-391. ----------------------------- Resolution: Done Fixed by splitting out <end-task/> from <end-conversation/>. Need a doco update! > <end-conversation /> ends task > ------------------------------ > > Key: JBSEAM-391 > URL: http://jira.jboss.com/jira/browse/JBSEAM-391 > Project: JBoss Seam > Issue Type: Bug > Components: BPM > Affects Versions: 1.1.0.BETA2 > Environment: CVS @ 13:50 -0000 2006/11/06 > Reporter: Peter Muir > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > Attachments: pageflow-transition-endTask.patch, pageflow-transition.patch > > > The reference manual says 'Optionally, we can specify a transition name. In this case, Seam will signal the end of the current task in the overarching business process.' (4.2.5) > Whether or not you specify a transition on <end-conversation /> if a task instance is active then it will be ended. > This is because in Page.java the execute method has > if ( transition == null ) > { > task.end(); > } > else > { > task.end(transition); > } > How about adding endTask="true|false" (default true) to end-conversation and altering Page.java accordingly? > This functionality would be useful if you want to 'cancel' out of a pageflow and returrn to the task at a later date. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-199) <conversation-end create-process="processDefinitionName"/>

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-199?page=all ] Gavin King closed JBSEAM-199. ----------------------------- Fix Version/s: 1.1.0.CR1 Resolution: Done > <conversation-end create-process="processDefinitionName"/> > ---------------------------------------------------------- > > Key: JBSEAM-199 > URL: http://jira.jboss.com/jira/browse/JBSEAM-199 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Priority: Minor > Fix For: 1.1.0.CR1 > > > This can be done with the annotations, but not from within a pageflow XML. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-489) IllegalStateException during session timeout

by Gavin King (JIRA)

IllegalStateException during session timeout -------------------------------------------- Key: JBSEAM-489 URL: http://jira.jboss.com/jira/browse/JBSEAM-489 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 conversation-scoped components don't get destroyed cleanly at session timeout, because the conversation context is not bound to the thread. -- 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

18 years, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-391) <end-conversation /> ends task

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-391?page=all ] Gavin King updated JBSEAM-391: ------------------------------ Fix Version/s: 1.1.0.CR1 Assignee: Gavin King > <end-conversation /> ends task > ------------------------------ > > Key: JBSEAM-391 > URL: http://jira.jboss.com/jira/browse/JBSEAM-391 > Project: JBoss Seam > Issue Type: Bug > Components: BPM > Affects Versions: 1.1.0.BETA2 > Environment: CVS @ 13:50 -0000 2006/11/06 > Reporter: Peter Muir > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > Attachments: pageflow-transition-endTask.patch, pageflow-transition.patch > > > The reference manual says 'Optionally, we can specify a transition name. In this case, Seam will signal the end of the current task in the overarching business process.' (4.2.5) > Whether or not you specify a transition on <end-conversation /> if a task instance is active then it will be ended. > This is because in Page.java the execute method has > if ( transition == null ) > { > task.end(); > } > else > { > task.end(transition); > } > How about adding endTask="true|false" (default true) to end-conversation and altering Page.java accordingly? > This functionality would be useful if you want to 'cancel' out of a pageflow and returrn to the task at a later date. -- 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

18 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006