Today is Saturday, 21st October 2017

Archive for the ‘Java’ Category


Java IDEs: Which IDE is in Most Demand in the Job Market?

Hi All,

A lot of new students ask me which Java IDE should they use. Eclipse, IntelliJ, NetBeans etc. My answer is … which ever tool you are comfortable with and most productive. However, I also tell them to pick an IDE that is in demand in the job market. Now granted, another IDE may be better on technical merits, but in this case, I like to use the tool that is most requested by employers.

Here’s a nice graph that shows the demand of Java IDEs in the Job Market.

Source: https://www.indeed.com/jobtrends/q-eclipse-q-intellij-q-netbeans.html

Share


JMS Tutorial Resources

Hi All,

I’ve had a number of students ask me about Java Message Service (JMS). They are eager to learn how to send/recieve messages using JMS. I’ve put together a list of free tutorial resources. Enjoys!

JMS Tutorial from Java EE 7 Tutorial
https://docs.oracle.com/javaee/7/tutorial/jms-concepts.htm#BNCDQ

JMS Tutorial with ActiveMQ
https://dzone.com/articles/jms-activemq

And, if you are interested in using JMS with Spring then here are some good links

Spring JMS Example
https://examples.javacodegeeks.com/enterprise-java/spring/spring-jms-example/

Getting Started with Spring JMS
http://www.baeldung.com/spring-jms

Messaging with Spring JMS
https://spring.io/guides/gs/messaging-jms/

Share


How To View Hibernate SQL Parameter Values

When using Hibernate, if you log the Hibernate SQL statements, you will see this:

However, for debugging your application, you want to see the actual parameter values in the Hibernate logs. Basically, you want to get rid of the question marks in the Hibernate logs.

You can view the actual parameters by viewing the low-level trace of the Hibernate logs. This is not set up by default. However, we can add log4j to allow us to see these low-level logs.

Here is an overview of the process:

1. Add log4j to your project classpath
2. Add log4j.properties to your “src” directory


Here are the detailed steps:

1. Add log4j to your project classpath

1a. Download log4j v1.2.17 from this link:
http://central.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar

1b. Copy this file to your project’s lib directory

bind-parameters-log4j-jar-file

1c. Right-click your Eclipse project and select Properties

1d. Select Build Path > Libraries > Add JARS…

1e. Select the log4j-1.2.17.jar file from the lib directory

bind-parameters-log4j-jar-build-path

 

2. Add log4j.properties to your “src” directory

2a. Copy the text from below

2b. Save this file in your “src” directory

bind-parameters-log4j-properties

Note: This file has an important setting:

This allows you see a low-level trace of Hibernate and this allows you see the real SQL parameter values.


Now run your application. You will see a lot of low-level TRACE logs in the Eclipse Console window.

Right-click in the Eclipse Console window and select Find/Replace…

Search for: binding parameter

You will see the logs with the real parameter values. Congrats!

bind-parameters-output

Share