[jboss-jira] [JBoss JIRA] Commented: (JBSEAM-303) Treat unnamed transition as default one

Raul Piaggio (JIRA) jira-events at jboss.com
Thu Jul 13 03:41:13 EDT 2006


    [ http://jira.jboss.com/jira/browse/JBSEAM-303?page=comments#action_12339491 ] 
            
Raul Piaggio commented on JBSEAM-303:
-------------------------------------

I tend to disagree.

I'm thinking of the following scenarios: an action has several outcomes and
that action is called from different pageflows. But not all pageflows are
interested in all the outcomes. Having a "default" treatment for all
outcomes not of interest is convenient. Similarly, a page may have buttons
or links to trigger several links but in some pageflows we know that only
one is rendered.

Again, this is all about a bit of convenience. It is not a big thing and I
don't think Seam's usability is affected at all without this feature.

What I'm really looking forward to is pageflow composition.

I am still confused about the <start-page> use. It seems to behave like
<start-state> when you start the pageflow but it can also behave as a <page>
if you jump to it from another node (and it has a view-id). Is this right?

-----Mensaje original-----
De: Gavin King (JIRA) [mailto:jira-events at jboss.com] 
Enviado el: miércoles, 12 de julio de 2006 20:40
Para: rpiaggio at handsoft.com.uy
Asunto: [JBoss JIRA] Commented: (JBSEAM-303) Treat unnamed transition as
default one

    [
http://jira.jboss.com/jira/browse/JBSEAM-303?page=comments#action_12339478 ]

            
Gavin King commented on JBSEAM-303:
-----------------------------------

The unnamed transition is triggered whenever the action returns a null
outcome to the JSF NavigationHandler.

I don't think it would be right to trigger the unnamed transition when the
outcome explicitly names a transition....would it?

or decision) node, the flow will fail to land on a page node, resulting in a
runtime exception (ClassCastException on
org.jboss.seam.core.Pageflow.getPage()).
to="menu"></transition>, without "name" property) trigger it when no other
transition maches.

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

        

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.10/386 - Release Date: 12/07/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.10/386 - Release Date: 12/07/2006
 



> Treat unnamed transition as default one
> ---------------------------------------
>
>                 Key: JBSEAM-303
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-303
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: BPM
>            Reporter: Raul Piaggio
>         Assigned To: Gavin King
>            Priority: Minor
>
> In a pageflow, whenever there's no matching transition on a (start-state or decision) node, the flow will fail to land on a page node, resulting in a runtime exception (ClassCastException on org.jboss.seam.core.Pageflow.getPage()).
> Suggestion: if there's an unnamed transition (i.e: <transition to="menu"></transition>, without "name" property) trigger it when no other transition maches.

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

       




More information about the jboss-jira mailing list