StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16433740
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2013-05-08T06:05:43.100
FavoriteCount
0
LastActivityDate
2013-05-08T18:02:34.363
LastEditDate
2013-05-08T18:02:34.363
LastEditorUserId
1001027
OwnerUserId
1001027
ParentId
16433623
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The equivalent to the <code>Provider</code> of guice is the <a href="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/beans.html#beans-factory-extension-factorybean" rel="nofollow"><code>FactoryBean</code></a> in Spring. From the documentation: <blockquote> The FactoryBean interface is a point of pluggability into the Spring IoC container's instantiation logic. If you have complex initialization code that is better expressed in Java as opposed to a (potentially) verbose amount of XML, you can create your own FactoryBean, write the complex initialization inside that class, and then plug your custom FactoryBean into the container. </blockquote> Sample <pre><code>public class MyFactoryBean implements FactoryBean<MyClassInterface> { @Override public MyClassInterface getObject() throws Exception { return new MyClassImplementation(); } @Override public Class<?> getObjectType() { return MyClassInterface.class; } @Override public boolean isSingleton() { return true; } } </code></pre> This is a good approach when you have external libraries and complex object creation to avoid long XML configuration to setup your beans. In order to use it within your context, you could just provide it as a normal bean within your context XML like: <pre><code>... <bean id="myClass" class="foo.bar.MyFactoryBean" /> ... </code></pre> BUT, if your bean is quite simple to be instantiated (not lots of dependencies), you can setup it directly on the context XML like: <pre><code><bean id="myClass" class="foo.bar.MyClassImplementation" /> </code></pre> Alternative If you use Spring 3 you could write a configuration class (class annotated with <code>@Configuration</code>) as documented <a href="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/beans.html#beans-java" rel="nofollow">here</a>. With this approach you could do something like: <pre><code>@Configuration public class MyConfiguration { @Bean public MyClassInterface getMyClass() { return new MyClassImplementation(); } } </code></pre> This would add your instance to spring context and let autowire it within other classes. But some configuration is required, and its quite easy following the documentation provided.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEquivalency of Guice Provider in Spring
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USFrancisco Spaeth
UserOwnerUserId
1. USFrancisco Spaeth
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEquivalency of Guice Provider in Spring
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.