img
Figure 21-8. The SpringBlog DOM
As shown in Figure 21-8, there are some differences between the DOM and the data model in Figure
21-7:
Both the Entry and Comment classes extend the AbstractBlogPosting class, which
·
contains the common properties and behavior of an entry, whether it's a blog
entry or comment. However, you will not see a table for the abstract class. It's the
same case for the Attachment class. In addition, the AbstractBlogPosting class
implements the BlogPosting interface, which the AOP obscenity filter will be
based on whether or not the target object had this interface implemented to
determine whether checking and obfuscation of obscenities are required.
The relationship between the AppUser and Role classes is many-to-many, because
·
an user can be granted multiple roles, and a role can be assigned to many users.
From the data model, you will see a join table (USER_ROLE_DETAIL) that holds the
relationship. While in the DOM, you will not see a class for the join table.
The Category class has a self-referencing relationship to itself to indicate the
·
hierarchy of the parent and subcategories.
The UML Model
The UML model contains various diagrams that reflect the behavior of the classes within the application.
There are two main types of UML diagrams, namely, static and dynamic diagrams. A static diagram
Search WWH :
Custom Search
Previous Page
Spring Framework 3 Topic Index
Next Page
Spring Framework 3 Bookmarks
Home