Skip to content
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.

Implement REST service with Akka HTTP #1

Closed
tdauth opened this issue Oct 23, 2018 · 2 comments
Closed

Implement REST service with Akka HTTP #1

tdauth opened this issue Oct 23, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@tdauth
Copy link
Contributor

tdauth commented Oct 23, 2018

Akka HTTP is not a real framework but a suite of libraries. Since we do not provide a web application here but a simple REST interface, it should be sufficient.

TODO instead of using rest.model, map our types from api into JSON and back.

@tdauth tdauth added the enhancement New feature or request label Oct 23, 2018
@tdauth tdauth self-assigned this Oct 23, 2018
tdauth added a commit that referenced this issue Oct 23, 2018
tdauth added a commit that referenced this issue Oct 25, 2018
- Add custom JSON formatter for our Map type
- Move Furrer model into seprate package since it is not valid
- Separate persistence layer into separate package
- Add Bash scripts for REST calls
- Simplify documentation
tdauth added a commit that referenced this issue Oct 25, 2018
- Fix marshalling and unmarshalling for ID based maps and add unit test.
- Allow deletion of applications and add unit test.
- Revert inheritance of Map which does not work with case classes.
- Add Bash scripts with REST calls.
tdauth added a commit that referenced this issue Oct 26, 2018
tdauth added a commit that referenced this issue Oct 26, 2018
- Cover all missing cases for the resources.
- Cover the web server app.
- Cover Id.compare.
@tdauth
Copy link
Contributor Author

tdauth commented Nov 5, 2018

Drop the REST API for applications, test suites, test cases etc. and replace it by the REST API for the state machines only.
The types in model and dsl should be adapted to the types in api.

tdauth added a commit that referenced this issue Nov 12, 2018
…n REST support #1 #4

- Store descriptors per state and define getDescriptors in the trait State.
- Fix comment about legacy code.
- Add State.addTransition.
- Remove all the DSL code which was experimental.
- Remove all the REST applications/test suites code which was experimental.
- Move model into rest.model.
- Adapt unit tests.
@tdauth tdauth changed the title Implement REST service with a Scala framework Implement REST service with Akka HTTP Nov 14, 2018
tdauth added a commit that referenced this issue Nov 15, 2018
… methods #1 #7 #9

- Besides, update some scalastyle rules.
- Move all sbt plugins to one file.
- Do some refactoring, so we only used immutable data structures.
- Add type ActionTransitions which stores the execution times.
- Initial persistence methods.
- Add initial Swagger support for the REST service.
tdauth added a commit that referenced this issue Nov 15, 2018
- Don't use any custom model package types but the types from the api package
for REST.
- GuiStateMachineApi works now with IDs for the state machines.
This allows the removal and retrieval of state machines based on the unique ID.
- Remove persistence layer since the Scala API provides persistence calls.
- Add bodys for the parameters for `get-state` and `execute-action`.
- Only use one service class GuiStateMachineService.
- Swagger uses the correct service class now (not RestService).
- Add initial JsonFormat types for all the required Scala API types.
- Remove model package and Bash scripts for the old REST API.
- Simplify documentation.
- Adapt unit tests.
@tdauth
Copy link
Contributor Author

tdauth commented Apr 11, 2019

A REST/Bolt service can be used with Neo4J, see #19 .

@tdauth tdauth closed this as completed Apr 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant