I have a web-app (Java, Hibernate Spring [MVC, Security, ...], JSP) and the packets structure is this way:
- entity (related to Hibernate)
- dao (access to DB)
- service (main logic)
- serviceobjects (used in services)
- controller
- bean (sent from Controllers to user)
- entitymapper & beanmapper (~converters)
- reader & builder (special objects which do some business logic, used in services)
- util (utils, like "get first element of Collection")
Does this structure match the MVC pattern?
- If YES, then what is the M-Model here exactly?
- If NO, then how could I describe such architecture?
Aucun commentaire:
Enregistrer un commentaire