StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2170710
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-31T05:48:07.750
FavoriteCount
0
LastActivityDate
2010-10-18T21:58:25.653
LastEditDate
2010-10-18T21:58:25.653
LastEditorUserId
87789
OwnerUserId
87789
ParentId
2019042
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Daniel, I have used one controller per page, one service and one dao per entity. <ul> <li>Use case logic goes in the controller</li> <li>Entity specific business logic goes in entity service. </li> <li>Actions which span multiple entities you can create a facade service - something which sits between controller and entity services</li> </ul> While the above is a good and practical approach, ideally: <ul> <li>you could break out any non MVC code from controller into its own service class, ie. 1 service class per page</li> <li>you should only access the entity dao via the entity service. </li> </ul> Here's how the control would flow: Ideally: UI -> PageController.java -> PageService.java -> EntityService.java -> EntityDao.java Practically, you could trim down a few layers: UI -> PageController.java -> EntityService.java Or for actions touching multiple entities: UI -> PageController.java -> Facade.java -> Entity1Service.java,Entity2Service.java PageController.java would be a Seam @Component and in your ui you can refer it as: <code>#{pageController}</code> and pull the data from the view. In architecture, the most important thing is how you layer things in the stack is avoid circular dependencies between layers. For example, Entity Service should not reference Controller and so on. The other important thing is to be consistent about layering in the entire application. Use code generators if you can to keep your code consistent across the application, it really pays off for large projects. Look into <a href="http://www.clickframes.org" rel="nofollow noreferrer">Clickframes</a> if you are interested in code generation (Clickframes generates starter code for Seam apps with full JPA/valdiation/security support which you can then modify). See this <a href="http://code.google.com/p/clickframes-seam-issuetracker-demo/" rel="nofollow noreferrer">Seam demo</a> build with Clickframes if interested.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSeam application Architecture
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVineet Manohar
UserOwnerUserId
1. USVineet Manohar
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.