eleonoradm / mobilelele Goto Github PK

sort of workaround (which means not applicable in the practice) to replace the usage of Spring Security that will be learned in the next module.
1.create CurrentUser class at a separate Security package - should contain @component and @SessionScope annotations.
It will be used with DI at the LoginController class.
2.use dependency spring-security-crypto (usually comes with Spring Security) for password hashing instead of saving them as plain text. Use it to create a new @bean for PasswordEncoder at the config class that will be injected as a final property at the DBInitializer class.
3.create UserRepository interface and inject it into the DBInitializer class.
4.create UserCredentialsContainer class as a storage model for the login data from the post request;

to consider changing the DB initialization through data.sql file in resources

1.create OfferController class - @controller annotation;
2.create OfferRepository interface (@repository upon the interface) and inject it into the DBInitializer constructor ;
3.populate the Offer table with some data;
4.to create OfferSummaryDTO and DTO for the fully detailed offer;
5.to create OfferServiceImpl class with a method that returns all offers (@service upon the impl) -> DI as a final property into the OfferController;