Robert von Burg
89739717f2
This is required because in certain instances it is important to lock the object before retrieving it, otherwise if, for instance in execution, we would need to fetch, lock and re-fetch to be sure we have the latest object. In moste of the Update*Commands this is not important as we perform a list commit wins, where the client wants their version to be persisted. Later a optimistic locking can be performed in that the given version must be the latest, otherwise an exception would be thrown |
||
---|---|---|
dev | ||
li.strolch.agent | ||
li.strolch.bom | ||
li.strolch.model | ||
li.strolch.performancetest | ||
li.strolch.persistence.postgresql | ||
li.strolch.persistence.xml | ||
li.strolch.planningwebapp | ||
li.strolch.privilege | ||
li.strolch.rest | ||
li.strolch.service | ||
li.strolch.testbase | ||
li.strolch.tutorialapp | ||
li.strolch.tutorialwebapp | ||
li.strolch.utils | ||
li.strolch.website | ||
li.strolch.xmlpers | ||
strolch_minimal | ||
strolch_minimal_rest | ||
.gitignore | ||
LICENSE | ||
README.md | ||
createBundle.sh | ||
deploy.sh | ||
hotfix.sh | ||
pom.xml | ||
release.sh | ||
setVersion.sh |
README.md
Strolch
The main repository which contains all of Strolch.
Strolch consists of the following modules:
- li.strolch.utils
- li.strolch.privilege
- li.strolch.agent
- li.strolch.model
- li.strolch.persistence.postgresql
- li.strolch.persistence.xml
- li.strolch.rest
- li.strolch.service
- li.strolch.testbase
With the following test applications:
- li.strolch.tutorialapp
- li.strolch.tutorialwebapp
- li.strolch.planningwebapp
- strolch_minimal
- strolch_minimal_rest
And of course the website itself:
- li.strolch.website
Find more to Strolch at our website: http://strolch.li