StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10453533
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-04T17:33:58.020
FavoriteCount
0
LastActivityDate
2012-05-04T17:42:22.773
LastEditDate
2012-05-04T17:42:22.773
LastEditorUserId
869854
OwnerUserId
869854
ParentId
10453242
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
When using dependency injection, you rely on the container to inject your objects dependencies instead of creating them yourself during execution. For example: Without using dependency injection I would have to write something like this: <pre><code>public class ATMTransferService { private AccountDAO accountDAO; public void transfer(Account from, Account to){ AccountDAO accountDAO = new AccountDAO(); ...Code that transfers money from one account to another and saves it... accountDAO.store(); } </code></pre> Notice that I had to instantiate accountDAO myself, and the responsibility of getting my dependancies was handled by myself. By using spring or some other framework that allows for DI, I would transfer that responsibility tothe container, by writing something like: <pre><code><bean id="ATMTransfer" class="com.example.ATMTransferService" > <property name="accountDAO" ref="AccDAO" /> </bean> <bean id="AccDAO" class="com.model.AccountDAO"> <property name="sessionFactory" ref="sessFac" </bean> <bean id="sessFac" class="..." //Dependencies required for the cration fo session factory. </bean> </code></pre> Now my class would like like this: public class ATMTransferService { private AccountDAO accountDAO; <pre><code>public void transfer(Account from, Account to){ ...Code that transfers money from one account to another and saves it... accountDAO.store(); } </code></pre> In this case, I've ommited the AccountDAO class, but it would have a dependency on a SessionFactory. You could also use a pre-defined constructor instead of using the default constructor by specifying it on the xml configuration. I hope i haven't simplified it too much, once the benefits of dependency injection are greater than this, you could swap implementation classes by just modifying an xml configuration for starters. You also get a much cleaner code once you remove dependency creation code from your business classes. It is really a great manner to promote interface oriented programming.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORegarding Dependency Injection principle in simple java class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USeduardohl
UserOwnerUserId
1. USeduardohl
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.