Nit's Cookbook

Introduction Recently I got an opportunity to work with spring data repositories. Its an excellent feature of Spring. you no longer need to manage writing basic crud operation logic for your application with this architecture. In a way like Hibernate sans the clumsy .hbm files and any sort of database awareness.  The key components of this architecture are : Rep ository  - This class would correspond to the Database and extends  PagingAndSortingRepository   Domain  - The object for which crud operations are needed Delegate - This class would be a handler for handling the request and returning the response. The implementation of handler would have the exact logic of the business involved. The goal of Spring Data repository abstraction is to significantly reduce the amount of  unintelligent code required to implement data access layers for various persistence stores. Key Concepts The central interface here would be the  Repository . The domain class a

Introduction Logback is a successor to the old school log4j. Logback constitues of 3 modules : logback-core :  This module lays the groundwork for the other two modules. logback-classic : Offers a native implementation of the SLF4J API. logback-access : This log generated when a user accesses a web-page on a web server. Logback-classic module requires the presence of slf4j-api.jar and logback-core.jar in addition to logback-classic.jar on the classpath. The logback-*.jar files are part of the logback distribution whereas slf4j-api-1.7.5.jar ships with SLF4J , a separate project. Why use Logback? According to me the striking feature of Logback are: Faster, smaller, higher mileage. Modular Architecture Easily integrates with legacy systems. Highly configurable. You can find detailed list of advantages straight from the horses mouth here .

What is RabbitMQ? RabbitMQ  is a messaging broker - an intermediary for messaging. It gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. Why do we need a message broker? Messaging enables software applications to connect and scale. Applications can connect to each other, as components of a larger application, or to user devices and data. Messaging is asynchronous, decoupling applications by separating sending and receiving data.

A nice to have list of instantiable and non-instantiable portlets: Non-Instanceable:- 1. Collaboration Blogs Blog Aggregator Calendar Message Boards Recent Bloggers Wiki 2. Community Bookmarks My Communities Page Comment Invitation Page Comments Page Flags Page Ratings 3. Content  Management Document Library Image Gallery Recent Documents Web Content Search  4. Entertainment Words 5. Finance Currency Converter Loan Calculator