StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6353250
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-06-15T05:05:08.737
FavoriteCount
0
LastActivityDate
2011-06-15T05:05:08.737
LastEditDate
LastEditorUserId
0
OwnerUserId
720599
ParentId
6351082
PostTypeId
2
Score
21
ViewCount
0
LastEditorDisplayName
text
Body
You can use the <code>BeanPostProcessor</code> interface, which is called by the <code>ApplicationContext</code> for all created beans, so you have the chance to fill the appropriate properties. I created a simple implementation, which does that: <pre><code>import java.lang.reflect.Field; import java.util.List; import net.vidageek.mirror.dsl.Mirror; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.springframework.beans.BeansException; import org.springframework.beans.factory.config.BeanPostProcessor; import org.springframework.stereotype.Component; @Component public class LoggerPostProcessor implements BeanPostProcessor { @Override public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException { List<Field> fields = new Mirror().on(bean.getClass()).reflectAll().fields(); for (Field field : fields) { if (Logger.class.isAssignableFrom(field.getType()) && new Mirror().on(field).reflect().annotation(InjectLogger.class) != null) { new Mirror().on(bean).set().field(field).withValue(LoggerFactory.getLogger(bean.getClass())); } } return bean; } @Override public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException { return bean; } } </code></pre> You don't have to do any complex registration step, since the <code>ApplicationContext</code> is capable of recognizing <code>BeanPostProcessor</code> instances and automatically register them. The <code>@InjectLogger</code> annotation is: <pre><code>import java.lang.annotation.Retention; import java.lang.annotation.RetentionPolicy; @Retention(RetentionPolicy.RUNTIME) public @interface InjectLogger { } </code></pre> And then you can easily use the annotation: <pre><code>public static @InjectLogger Logger LOGGER; ... LOGGER.info("Testing message"); </code></pre> I used the <a href="http://projetos.vidageek.net/mirror/mirror/" rel="noreferrer">Mirror</a> library to find the annotated fields, but obviously you may perform a manual lookup in order to avoid this additional dependency. It's actually a nice idea to avoid repeated code, and even small issues that come from copying and paste the <code>Logger</code> definitions from other classes, like when we forget to change the <code>class</code> parameter, which leads to wrong logs.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing java annotation to inject logger dependency
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRedder
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. COVery cool solution. If you want to group logging by package or a set of classes you could use this solution to move that configuration in XML. Also, a very nice complete answer with clear examples.
 singulars
 PostPostId
 PO
 UserUserId
 USPace

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.