StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12231002
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-01T20:06:35.343
FavoriteCount
0
LastActivityDate
2013-03-05T21:53:28.160
LastEditDate
2013-03-05T21:53:28.160
LastEditorUserId
241986
OwnerUserId
241986
ParentId
12229282
PostTypeId
2
Score
53
ViewCount
0
LastEditorDisplayName
text
Body
<code>@Component</code> and <code>@Configuration</code> are indeed very different types of annotations. <code>@Component</code> and similar annotations (<code>@Service</code>, <code>@Repository</code>, etc. )and its <a href="http://jcp.org/aboutJava/communityprocess/final/jsr330/index.html" rel="noreferrer">JSR-330</a> counterpart <code>@Named</code> allow you to declare beans that are to be picked up by autoscanning with <code><context:component-scan/></code> or <code>@ComponentScan</code> they register the bean definition for the classes, so they are roughly equivalent to declaring the specified beans with the <code><bean ... /></code> tag in XML. This bean types will adhere to the standard proxy creation policies. <code>@Configuration</code> annotation was designed as the replacement of the XML configuration file. To create <code>@Configuration</code> annotated beans, Spring will always use <code>CGLIB</code> to subclass the <code>@Configuration</code> annotated class, overriding its <code>@Bean</code> annotated method to replace it with the bean lookup method to make singleton beans to be created only once. (Spring does not use <code>CGLIB</code> to intercept internal method calls of normal Spring beans, it creates a separate instance of proxy instead(same way like JDK proxy does). Doing so allows to use proxies to avoid cardinality mismatch - for example a proxy singleton can fetch current session bean, which is not possible with class inheritance only. ). Despite that, <code>@Configuration</code> annotated classes are still able to use annotated(<code>@Autowired</code>, <code>@Inject</code> etc.) fields and properties to request beans (and even other <code>@Configuration</code> annotated beans too) from the container. Example from 4.12.5 section of the <a href="http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/beans.html#beans-java" rel="noreferrer">documentation</a> <pre><code>@Configuration public class AppConfig { @Bean public ClientService clientService1() { ClientServiceImpl clientService = new ClientServiceImpl(); clientService.setClientDao(clientDao()); return clientService; } @Bean public ClientService clientService2() { ClientServiceImpl clientService = new ClientServiceImpl(); clientService.setClientDao(clientDao()); return clientService; } @Bean public ClientDao clientDao() { return new ClientDaoImpl(); } } </code></pre> in the example above only one <code>ClientDao</code> instance will be created. <code>@Autowired</code> is Spring annotation, while <code>@Inject</code> is a JSR-330 annotation. <code>@Inject</code> is equivalent to <code>@Autowired</code> or <code>@Autowired(required=true)</code>, but you can't get <code>@Autowired(required=false)</code> behavior with the JSR-330 <code>@Inject</code>annotation. This annotation always uses by-type autowiring. Spring implements <a href="http://jcp.org/en/jsr/detail?id=250" rel="noreferrer">JSR-250</a> <code>@Resource</code> annotation in a rather special way. <code>@Resource</code> was originally designed for locating JNDI resources in Java EE, but Spring widens it applicability making it possible to wire to any bean in the container(JNDI resources are available as beans with the help of <a href="http://static.springsource.org/spring/docs/3.1.x/javadoc-api/org/springframework/jndi/support/SimpleJndiBeanFactory.html" rel="noreferrer">SimpleJndiBeanFactory</a>). The name of the corresponding bean can be specified as <code>name</code> attribute of <code>@Resource</code> annotation, if no name was specified, then the name of the annotated field or property will be used. Another strange feature is that if no bean with the property name was found spring will fallback to by-type wiring. Example Imagine that we have an <code>AlphaClass</code> bean named beanAlpha and a <code>BetaClass</code> bean beanBeta in the container. <pre><code>@Resource BetaClass something; // Wires to beanBeta - by-type @Resource BetaClass beanAlpha; // Will throw exception, because "beanAlpha" is not BetaClass -> it's a bad idea to use @Resource as a replacement of @Autowired @Resource Object beanAlpha; //Wires to beanAlpha - by-name </code></pre> So it's a good practice to always specify resource name explicitly when using <code>@Resource</code> annotation. Documentation <a href="http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/beans.html#beans-java" rel="noreferrer">Spring annotations</a> <a href="http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/beans.html#beans-standard-annotations" rel="noreferrer">Bean standard annotations</a> update fixed JSR references as shevchik has pointed out. DI specific annotations are provided by JSR-330, which was developed by Google (Guice Framework) and SpringSource(Spring Framework) engineers. <code>@Resource</code> is JNDI based and provided by <a href="http://jcp.org/en/jsr/detail?id=250" rel="noreferrer">JSR-250</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODifference between Spring annotations
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBoris Treukhov
UserOwnerUserId
1. USBoris Treukhov
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODifference between Spring annotations
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. CO"@Named and @Inject" are JSR330 annotations. "@Resource, @PostConstruct, @PreDestroy" are JSR250.
 singulars
 PostPostId
 PO
 UserUserId
 USSergii Shevchyk

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.