diff --git a/spring-webflow/src/main/java/org/springframework/webflow/core/collection/package.html b/spring-webflow/src/main/java/org/springframework/webflow/core/collection/package.html index 51479014..66dcdaba 100644 --- a/spring-webflow/src/main/java/org/springframework/webflow/core/collection/package.html +++ b/spring-webflow/src/main/java/org/springframework/webflow/core/collection/package.html @@ -6,10 +6,9 @@ Core element collection types used within Spring Web Flow.
This packages defines two primary collection flavors:
Each map is java.util.Map adaptable.
-Core, stable abstractions for representing flow definitions. -
--Each flow has an indentifier and is composed of one or more states, one of which is the start state. -States may be transitionable, and if so define one or more transitions that lead to other states. -
--With these types a client can introspect a flow definition to reason on its attributes and traverse -its structure, perhaps to display a visual diagram. Note that the types defined in this package -do not capture the behavioral characteristics of a flow. -
--The following code shows the beginnings of a basic flow definition traversal algorithm: -
- FlowDefinition flow = ...
-
- // lookup start state
- StateDefinition state = flow.getStartState();
-
- // traverse to state transitions
- traverse(state);
-
- public void traverse(StateDefinition state) {
- logger.info("State: " + state.getId());
- while (state instanceof TransitionableStateDefinition) {
- TransitionableStateDefinition transitionable = (TransitionableStateDefinition)state;
- TransitionDefinition[] transitions = transitionable.getTransitions();
- for (int i = 0; i < transitions.length; i++) {
- Transition t = transitions[i];
- logger.info("Transition " + t.getId());
- traverse(state.getOwner().getState(t.getTargetStateId());
- }
- }
- }
-
-
-
-
+
+
++Core, stable abstractions for representing flow definitions. +
++Each flow has an indentifier and is composed of one or more states, one of which is the start state. +States may be transitionable, and if so define one or more transitions that lead to other states. +
++With these types a client can introspect a flow definition to reason on its attributes and traverse +its structure, perhaps to display a visual diagram. Note that the types defined in this package +do not capture the behavioral characteristics of a flow. +
++The following code shows the beginnings of a basic flow definition traversal algorithm: +
+
+ FlowDefinition flow = ...
+
+ // lookup start state
+ StateDefinition state = flow.getStartState();
+
+ // traverse to state transitions
+ traverse(state);
+
+ public void traverse(StateDefinition state) {
+ logger.info("State: " + state.getId());
+ while (state instanceof TransitionableStateDefinition) {
+ TransitionableStateDefinition transitionable = (TransitionableStateDefinition)state;
+ TransitionDefinition[] transitions = transitionable.getTransitions();
+ for (int i = 0; i < transitions.length; i++) {
+ Transition t = transitions[i];
+ logger.info("Transition " + t.getId());
+ traverse(state.getOwner().getState(t.getTargetStateId());
+ }
+ }
+ }
+
+
+
\ No newline at end of file
diff --git a/spring-webflow/src/main/java/org/springframework/webflow/definition/registry/package.html b/spring-webflow/src/main/java/org/springframework/webflow/definition/registry/package.html
index 3a0d224c..cc26111d 100644
--- a/spring-webflow/src/main/java/org/springframework/webflow/definition/registry/package.html
+++ b/spring-webflow/src/main/java/org/springframework/webflow/definition/registry/package.html
@@ -7,6 +7,7 @@ The flow definition registry subsystem for managing containers of flow definitio
You can construct a generic, initially empty FlowDefinitionRegistry, populate it
with flow definitions using a FlowDefinitionRegistrar, then lookup flow definitions by id.
For example:
+
// create registry
FlowDefinitionRegistry registry = new FlowDefinitionRegistryImpl();
@@ -20,6 +21,5 @@ For example:
// use registry
FlowDefinition flow = registry.getFlow("myFlow");
-