StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10818703
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-30T14:48:23.553
FavoriteCount
0
LastActivityDate
2012-05-30T14:48:23.553
LastEditDate
LastEditorUserId
0
OwnerUserId
525036
ParentId
9734503
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
We were also having this issue and since we are required to configure the logging using Log4J this was an issue. However, using <code>prefer-application-packages</code> seems to work so far, i.e. putting a <code>weblogic-application.xml</code> file in the <code>META-INF</code> folder of the EAR with the following: <pre><code><?xml version="1.0" encoding="UTF-8"?> <weblogic-application xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-application.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" > <prefer-application-packages> <package-name>org.slf4j</package-name> </prefer-application-packages> </weblogic-application> </code></pre> (ok the specified xmlns is an old one but it works, you may update it if you want, I just took ours and removed the unrelated parts). We still have the aforementioned warning but it uses Log4J as required. In fact, if you look at <a href="http://www.slf4j.org/codes.html#multiple_bindings" rel="nofollow">the URL specified on the next line</a> in the logs (omitted here in the question), it says: <blockquote> The warning emitted by SLF4J is just that, a warning. SLF4J will still bind with the first framework it finds on the class path. </blockquote> So I guess it still uses the normal class-loading mechanism for loading <code>org.slf4j.impl.StaticLoggerBinder</code>, which we actually configured to prefer the one in our EAR (i.e. make it the first on the classpath). Yet, the warning remains but it works. Fixing the warning would be good but probably not possible without altering WebLogic's provided libraries.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPrevent Weblogic 12c from using system's slf4j binding
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDidier L
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.