The last couple of months have been a lot of fun as we’ve been working on IntelliJ IDEA 2017.2, which is due out this summer. We appreciate the contributions from all EAP participants and the feedback they’ve shared on the new features. We reached a feature-freeze two weeks ago, and today, with roughly a month before the release, we’re happy to give you a detailed glimpse of what’s noteworthy in the upcoming IntelliJ IDEA 2017.2.
If you can’t wait, download the public preview build right away and try it on your own. Otherwise, read on and learn about the major changes.
Tomcat by default ships with a couple of Realm implementations likeJDBCRealm, DataSourceRealm, and JNDIRealm, etc. But sometimes, it is not sufficient for your organization’s requirements and you are required to apply your own implementations.
How to Implement a Custom Realm in Tomcat
You can create your own realm by extending RealmBase class; here, I am going to show an example of implementing a new Realm in Tomcat.
JMS (Java Message Service) is a Java Message Oriented Middleware used to send messages between clients and works by sending messages to a message queue which are then taken when possible to execute a transaction. This post will focus on implementing JMS with Spring Boot, which doesn’t take long at all to setup.
JMS and message queues, in general, bring some certain advantages over using RESTful services such as:
Although I typically use Groovy to write JVM-hosted scripts to be run from the command-line, there are times when I need to parse command-line parameters in Java applications and there are a plethora of libraries available for Java developers to use to parse command-line parameters. In this post, I look at one of the best known of these Java command line parsing libraries: Apache Commons CLI.