Examples of org.apache.isis.core.specsupport.scenarios.ScenarioExecution$VariableId

org.apache.isis.core.specsupport.scenarios.ScenarioExecution

Key for objects stored by steps in the scenario.

Objects can be identified in a variety of manners:

a fully qualified object provides both its type and a (unique) id; for example 'lease OXF-TOPMODEL-001'
a named object provides only its id; for example 'OXF-TOPMODEL-001'
a typed object provides only its type; for example 'the lease'.

Because of the second rule, the id should be unique in and of itself.

The expectation is that scenarios will use the first form (fully qualified) the first time that an object is introduced within a scenario. Thereafter either of the other forms may be used. In the case of a typed object (eg "the lease"), the most recently "touched" object of that type is returned.

     * Not every class holding step definitions should have these hooks, only those that correspond to the logical
     * beginning and end of scenario.  As such, this method may only be called once per scenario execution
     * (and fails fast if called more than once).
     */
    protected void before(ScenarioExecutionScope scope) {
        final ScenarioExecution scenarioExecution = scope.instantiate();
        scenarioExecution.beginTran();
    }

Examples of org.apache.isis.core.specsupport.scenarios.ScenarioExecution$VariableId

Related Classes of org.apache.isis.core.specsupport.scenarios.ScenarioExecution$VariableId