Polish docs

- Add more info into what's new in 1.2.8
- Small polish
- Relates to #476
This commit is contained in:
Janne Valkealahti
2018-01-22 10:04:25 +00:00
parent c90baa2624
commit dfe3aa6b72
2 changed files with 8 additions and 6 deletions

View File

@@ -2596,8 +2596,7 @@ Actual _Repository_ implementation for a _JPA_ is
`JpaStateMachineRepository` which is backed by _Entity_ class
`JpaRepositoryStateMachine`.
Generic way to persist machine for jpa is shown below. This is
equivalent to machine shown in <<image-sm-repository-simplemachine>>.
Generic way to persist machine for jpa is shown below.
[source,java,indent=0]
----
@@ -2610,8 +2609,7 @@ Actual _Repository_ implementation for a _Redis_ is
`RedisStateMachineRepository` which is backed by _Entity_ class
`RedisRepositoryStateMachine`.
Generic way to persist machine for jpa is shown below. This is
equivalent to machine shown in <<image-sm-repository-simplemachine>>.
Generic way to persist machine for jpa is shown below.
[source,java,indent=0]
----
@@ -2624,8 +2622,7 @@ Actual _Repository_ implementation for a _MongoDB_ is
`MongoDbStateMachineRepository` which is backed by _Entity_ class
`MongoDbRepositoryStateMachine`.
Generic way to persist machine for jpa is shown below. This is
equivalent to machine shown in <<image-sm-repository-simplemachine>>.
Generic way to persist machine for jpa is shown below.
[source,java,indent=0]
----

View File

@@ -41,4 +41,9 @@ not seen in a point release but these changes didn't merit a fork of
_Spring Statemachine 1.3_.
* JPA entity classes have changed table names <<sm-repository-config-jpa>>
* New sample <<statemachine-examples-datajpapersist>>
* New _Entity_ classes for persistence <<sm-repository-persistence>>
used with <<sm-repository-persistence>>
* Transition conflict policy mentioned in
<<statemachine-config-commonsettings>>