StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4713314
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-17T12:48:58.290
FavoriteCount
0
LastActivityDate
2011-01-17T12:48:58.290
LastEditDate
LastEditorUserId
0
OwnerUserId
289060
ParentId
4708689
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I am not a Java expert, but I use NHibernate in my .NET code so my experience should be directly translatable to the Java world. When using ORM (like Hibernate you mentioned) to build Domain-Driven Design application, one of good (I won't say best) practices is to create so-called application services between the UI and the Domain. They are similar to stateless business objects you mentioned, but should contain almost no logic. They should look like this: <pre><code>public void SayHello(int id, String helloString) { SomeDomainObject target = domainObjectRepository.findById(id); //This uses Hibernate to load the object. target.sayHello(helloString); //There is a single domain object method invocation per application service method. domainObjectRepository.Save(target); //This one is optional. Hibernate should already know that this object needs saving because it tracks changes. } </code></pre> Any changes to objects contained by DomainObject (also adding objects to collections) will be handled by Hibernate. You will also need some kind of AOP to intercept application service method invocations and create Hibernate's session before the method executes and save changes after method finishes with no exceptions. There is a really good sample how to do DDD in Java <a href="http://dddsample.sourceforge.net/" rel="nofollow">here</a>. It is based on the sample problem from Eric Evans' <a href="http://rads.stackoverflow.com/amzn/click/0321125215" rel="nofollow">'Blue Book'</a>. The application logic class sample code is <a href="http://dddsample.svn.sourceforge.net/viewvc/dddsample/branches/1_1_x/dddsample/src/main/java/se/citerus/dddsample/application/impl/BookingServiceImpl.java?revision=436&view=markup" rel="nofollow">here</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODDD: Where to put persistence logic, and when to use ORM mapping
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSzymon Pobiega
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.