StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLogging provided jars by in-project loggers
primarykey
Id
8790180
data
AcceptedAnswerId
8791882
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-09T14:47:29.480
FavoriteCount
0
LastActivityDate
2012-01-09T16:40:35.070
LastEditDate
LastEditorUserId
0
OwnerUserId
1138884
ParentId
0
PostTypeId
1
Score
2
ViewCount
209
LastEditorDisplayName
text
Body
I would like to ask you a question about logging provided jars. I have maven application with many dependencies and i need to log it by using logback. I work on jboss 5.1. Almost everything works perfectly fine. I can log all actions from my packets by using logback.xml file and adequate appenders etc. :) There is one problem - I cannot log org.hibernate actions by using logback. It seems to log itself by using log4j in jboss (jboss-log4j.xml configures that). In my pom.xml i have org.hibernate in scope provided - it is provided by jboss naturally. <pre><code><dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-core</artifactId> <version>3.3.1.GA</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> <version>3.4.0.GA</version> <scope>provided</scope> </dependency> </code></pre> Snippet from logback.xml <pre><code><logger name="org.hibernate" level="TRACE" additivity="false"> <appender-ref ref="SQL_FILE" /> </logger> </code></pre> When i delete <pre><code><scope>provided</scope> </code></pre> from pom.xml it starts to log using logback.xml in project configuration. I would do that, but i have to use provided jars instead of my own. Is there any possibility to log provided jars by using in-project configuration? Or am I doomed and i have to use log4j configuration in jboss directory?
Tags
<hibernate><maven><jboss><logback>
Title
Logging provided jars by in-project loggers
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDeo
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POLogging provided jars by in-project loggers
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POLogging provided jars by in-project loggers
 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.