You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bit of confusion which of the interfaces in Salespoint describe consumable components and which of them are provided as Spring beans by default. This probably stems from the fact that most implementations are package private and thus – rightfully so – aren't even listed.
We should make this clear in the Javadoc, probably by also annotating the service interfaces with @Service.
The text was updated successfully, but these errors were encountered:
…otations.
As our implementation classes are package protected to avoid client code to refer to them, they don't appear in Salespoint's Javadoc. That makes it hard to identify which of the types are actually candidates for injection into student project's code.
We now explicitly annotate the public interfaces of those components with the Spring stereotype annotations although that sometimes wouldn't even be necessary (e.g. in the case of Spring Data repositories).
There seems to be a bit of confusion which of the interfaces in Salespoint describe consumable components and which of them are provided as Spring beans by default. This probably stems from the fact that most implementations are package private and thus – rightfully so – aren't even listed.
We should make this clear in the Javadoc, probably by also annotating the service interfaces with
@Service
.The text was updated successfully, but these errors were encountered: