| ... | ... | @@ -10,6 +10,7 @@ You have some possibilities to control server creation with Sparkling: |
|
|
|
* __Pick the methods__ that should be available via the server:
|
|
|
|
1. `Sparkling.startServer(..)` gives a parameter where you can specify the names of the methods that should not be used.
|
|
|
|
2. Annotate a method with `@Skip4Service`.
|
|
|
|
* Add default values to your method parameters with `@DefaultValue("myValue")` in order to omit them at request time.
|
|
|
|
* Add __several handler objects__ to the server with `Sparkling.addHandler2Server(..)`. You can specify a subpath for each handler object. The only difference to `Sparkling.startServer(..)` it that `Sparkling.startServer(..)` specifies the port of the server also.
|
|
|
|
* Make cleanups at __server shutdown__, when you e.g. have to close some database connections, with `Sparkling.addShutdownRoutine(Runnable runnable)`.
|
|
|
|
* __Suppress documentation__ creation with `createDocumentation=false` as parameter of `Sparkling.addHandler2Server(..)` and `Sparkling.startServer(..)`.
|
| ... | ... | |
