|
If you were logged in you would be able to see more operations.
|
|
|
| Release Notes Comment: |
The service pattern has been greatly simplified in 1.4 with a number of benefits. Most notably a huge reduction in the amount of boiler plate code needed and a clean separation between interface and implementation.
|
|
The Service pattern currently requires four classes per service: *Arg, *ArgImp, *Command, *Service. To use a service, it also has to be wired in the config system. This is all rather painful.
The ArgImp and Command classes can be easily generated by annotations. The wiring could also be created by annotation processors.
|
|
Description
|
The Service pattern currently requires four classes per service: *Arg, *ArgImp, *Command, *Service. To use a service, it also has to be wired in the config system. This is all rather painful.
The ArgImp and Command classes can be easily generated by annotations. The wiring could also be created by annotation processors. |
Show » |
| There are no comments yet on this issue.
|
|
Improvement
Closed
Major
Reduce boiler plate code in the Service pattern