StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
101049
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-09-19T10:50:31.337
FavoriteCount
0
LastActivityDate
2008-09-19T10:57:13.987
LastEditDate
2008-09-19T10:57:13.987
LastEditorUserId
18027
OwnerUserId
18027
ParentId
100922
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
Tahir Akhtar
text
Body
There is nothing wrong with this code and you can still use it with Dependency Injection frameworks like Spring and Guice. Many developers see Spring's XML configuration file as an advantage over wiring dependencies within code as you can switch implementations without needing a compilation step. This benefit actually is realized in situations where you already have several implementations compiled in your class path and you want to choose the implementation at deployment time. You can imagine a situation where a component is provided by a third party after deployment. Similarly there can be a case when you want to ship additional implementations as a patch after deployment. But not all DI frameworks use XML configuration. Google Guice for example have Modules written as Java classes that must be compiled like any other java class. So what is the advantage of DI if you even need a compilation step? This takes us back to your original question. I can see following advantages: <ol> <li>Standard approach to DI throughout application.</li> <li>Configuration neatly separated out from other logic. </li> <li>Ability to inject proxies. Spring for example allows you to do declarative Transaction handling by injecting proxies instead of your implementation</li> <li>Easier re-use of configuration logic. When you use DI extensively, you will see a complex tree of dependencies evolving over time. Managing it without a clearly separated out configuration layer and framework support can be a nightmare. DI frameworks make it easy to re-use configuration logic through inheritance and other means.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODefault constructor vs IOC container
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTahir Akhtar
UserOwnerUserId
1. USTahir Akhtar
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. 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.