References
- CPS-2240Getting issue details... STATUS
Issues & Decisions
Issue | Notes | Decision | |
---|---|---|---|
1 | use api and impl folders | Team agreed on separate top level ap and impl folders. Common impl folders can be at top level ie. not under impl. | |
2 | use feature based packages | Team agreed to use current 4 service as feature folders directly under api and impl
| |
3 | when to use common packages | when in doubt use common package ie exceptions might be re-used for otrerh features in teh futures | |
4 | scope | curerntly only ncmp-service in scope. | |
5 | plan | team agreed to do trial with 'datajobs' first. Code need to be reviewed by both teams. Once this is completed we will adress 'legacy' services |
Propose Generic structure
api\feature1\someService.class api\feature1\models\specificModelclass api\feature1\exceptions\sepcificException.class api\feature2\someService.class api\feature2\models\specificModelclass api\feature2\exceptions\sepcificException.class api\models\commonModel.class api\exeptions\commonexception.class impl\feature1\someServiceImpl.class impl\feature1\helperPackage\somHelper.class impl\feature2\someServiceImpl.class utils\commonHelper.class
DataJobs Structure
Proposed structure (not complete but indicative):
api\datajobs\DataJobsService.class api\datajobs\models\DataJobMetadata.class api\datajobs\models\DataJobReadRequest.class api\datajobs\models\DataJobWriteRequest.class impl\datajobs\DataJobsServiceImpl.class utils\AlternateIdMatcher.class