Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Try with the following in your <code>hibernate.cfg.xml</code> or in your <code>persistence.xml</code>:</p> <pre><code>&lt;property name="hibernate.show_sql"&gt;true&lt;/property&gt; &lt;property name="hibernate.use_sql_comments"&gt;true&lt;/property&gt; </code></pre> <p>Plus the following inside your <code>log4j.properties</code>:</p> <pre><code>log4j.rootLogger=INFO,stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.Threshold=INFO log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d{dd/MM/yyyy HH:mm:ss} %-5p %x - %m%n org.apache.commons.digester.Digester=INFO org.hibernate=INFO org.springframework.orm=DEBUG,stdout </code></pre> <p>I have no doubt you will have logs if you put these two files in the classpath of your webapp. </p> <p>With Maven, you should put these files inside the folder <code>src/main/resources</code>. They will be packaged inside the resulting <code>target</code> folder you will get if you do a 'mvn clean package`.</p> <p>To declare a slf4j logger, you should do this way:</p> <pre><code>public class User { public static final Logger logger = LoggerFactory.getLogger(User.class); //fields getters and setters... public User() { } public User(DTO userDTO) { this.username = userDTO.username; // etc. logger.debug("your user was initialized with the DTO, see this.toString()=?", this.toString()); } //etc. some other methods, if any //toString() public String toString() { //return a String representation of an User object. } } </code></pre> <p>And to limit a log level for a specific appender, you should use:</p> <pre><code>log4j.logger.appenderName.packageName.className=LEVEL </code></pre> <p>Note you are currently using:</p> <pre><code>log4j.logger.packageName.className=LEVEL </code></pre> <p>Good luck!</p>
    singulars
    1. This table or related slice is empty.
    1. POHibernate logging in Spring application on JBoss 7.1
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USThierryB
    1. USThierryB
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COUnfortunatelly this doesn't work. I don't know what I'm doing wrong. My pom.xml file is ok, right? I've put log4j.properties file to src/main/resources. In class *UserService* in package *services* there is a line `Logger.getLogger(getClass()).info(user);` which results in `20:46:52,449 INFO [services.UserService] (http-localhost-127.0.0.1-8080-1) User[id: null loginEmail: null alias: Asdf password: asdfasdfasdf]` Then I tried to limit it with *log4j.logger.services.UserService=WARN* in log4j.properties but it still shows up in logs. It seems like this file is still not used by log4j
      singulars
      1. PO
      1. USBladositto
    2. COYou have added the `slf4j` dependency in your `pom.xml` so it is possible that slf4j is used with default configuration. See edited response to have an example of slf4j usage inside a java class.
      singulars
      1. PO
      1. USThierryB
    3. COOk. That was great tip to use SLF4J logger instead of LOG4J's one. Although it still have not gained control over logging. Its driving me nuts. I'm starting to wonder if it's not my application servers fault? I'm using JBoss AS 7.
      singulars
      1. PO
      1. USBladositto
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload