Results 1 to 5 of 5

Thread: [SWF2.0.0] inheritance and subflows - Possible Bug

  1. #1
    Join Date
    Jul 2006
    Location
    London
    Posts
    500

    Default [SWF2.0.0] inheritance and subflows - Possible Bug

    Inherited flow doesn't work when returning to a sub-flow.

    Scenario:

    * Abstract flow definition of global menu transitions.

    * Flow starts then triggers a subflow.

    * Menu clicked when in subflow (results in error 'No transition found on occurrence of event')

    * Adding the GT transition (which should of been inherited) into subflow-state resolves the problem but defeats the point sadly.
    Regards,
    James

  2. #2
    Join Date
    Jul 2006
    Location
    London
    Posts
    500

    Default

    Workaround:

    Code:
    <subflow-state id="edit.subflow" subflow="some-flow">		
       .
       .	
       <transition on="*" to="${currentEvent}"/>  
    </subflow-state>
    Regards,
    James

  3. #3
    Join Date
    Feb 2008
    Location
    Nashua, NH
    Posts
    78

    Default

    James,

    I'm wondering if this is an issue with flow inheritance or with subflows using a global transition. Can you try moving the transition into the global-transitions block of the concrete flow definition.

    If that works, then this is an inheritance issue. If not it is a subflow issue.

    Either way, please open a JIRA.

    -Scott
    Scott Andrews

    Software Engineer, Web Products Team
    SpringSource

  4. #4
    Join Date
    Jul 2006
    Location
    London
    Posts
    500

    Default

    Adding the GT in the concrete flow did not resolve the problem.

    JIRA Opened
    http://jira.springframework.org/browse/SWF-665
    Regards,
    James

  5. #5
    Join Date
    Jul 2006
    Location
    London
    Posts
    500

    Default

    Scott

    Having looked into this further I don't think there is a problem with SWF2.0. I was missing a set of GT's to handle the end-state ID returned from the sub-flow.

    This was why my workaround <transition on="*" to="${currentEvent}" /> works because 'currentEvent' equals an inherited <end-state> which then starts a new flow via flowRedirect.

    Hope you didn't spend much time of looking into this yet!
    Regards,
    James

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •