code_junkie

OO vs. Layered; balancing “OO purity” with getting things done

Nov 11th, 2011
93
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.96 KB | None | 0 0
  1. class UserServlet {
  2. handleRequest() {
  3. String id = request.get("id");
  4. String name = request.get("name");
  5. if (UserBizLayer.updateUserName(id,name))
  6. response.setStatus(OK);
  7. else
  8. response.setStatus(BAD_REQUEST);
  9. }
  10. }
  11.  
  12. class UseBizLayer {
  13. updateUserName(String id, String name) {
  14. long key = toLong(id);
  15. user = userDAO.find(key);
  16. if user == null
  17. return false;
  18. if (!validateUserName(name))
  19. return false;
  20. user.setName(name);
  21. userDAO.update(user);
  22. return true;
  23. }
  24.  
  25. validateUserName(String name) {
  26. // do some validations and return
  27. }
  28. }
  29.  
  30. class User {
  31. long key;
  32. String name;
  33. String email;
  34.  
  35. // imagine getters/setters here
  36. }
  37.  
  38. public class UserModel extends DatabaseModel implements XMLable, CRUDdy, Serializable, Fooable, Barloney, Baznatchy, Wibbling, Validating {
  39. // member fields
  40. // getters and setters
  41. // 100 interface methods
  42. }
Add Comment
Please, Sign In to add comment