Java Insightz

1 [abc] a, b, or c (simple class) 2 [^abc] Any character except a, b, or c (negation) 3 [a-zA-Z] a through z or A through Z, inclusive (range) 4 [a-d[m-p]] a through d, or m through p: [a-dm-p] (union) 5 [a-z&&[def]] d, e, or f (intersection) 6 [a-z&&[^bc]] a through z, except for b and c: [ad-z] (subtraction) 7 [a-z&&[^m-p]] a through z, and not m through p: [a-lq-z](subtraction) X?  X, once or not at all X*  X, zero or more times X+  X, one or more times X{n}    X, exactly n times X{n,}   X, at least n times X{n,m}  X, at least n but not more than m times Reluctant quantifiers X?? X, once or not at all X*? X, zero or more times X+? X, one or more times X{n}?   X, exactly n times X{n,}?  X, at least n times X{n,m}? X, at least n but not more than m times Possessive quantifiers X?+ X, once or not at all X*+ X, zero or more times X++ X, one or more times X{n}+   X, exactly...

1. Copy & Paste Its one of the most powerful tool and technique in the typical programmer. But at the same time its too dangerous that you ought to forgot the code according to you requirements. So always be cautious about what piece of code you are copying. Read at least two to three times to avoid the tricky for fishy things while your unit testing. 2. Exception Catch Block. Always give priority to write some thing useful and meaning full statements in the exception catch block.It really worth when you troubling shooting the issues. Never leave this block with empty or sop's. And always throw the exception to the calling method. 3. String operations Since String is immutable object, when you do any operation on string that results a new object. So after you do any modifications on String and do assign the string some object and use it. 4. Null pointers Don't perform the operations on objects without checking the Object null condition. And while checking the...

  CRON expression.   Cron-Expressions are used to configure instances of CronTrigger. Cron-Expressions are strings that are actually made up of seven sub-expressions, that describe individual details of the schedule. These sub-expression are separated with white-space, and represent: Seconds Minutes Hours Day-of-Month Month Day-of-Week Year (optional field)       +-------------------- second ( 0 - 59 ) | +----------------- minute ( 0 - 59 ) | | +-------------- hour ( 0 - 23 ) | | | +----------- day of month ( 1 - 31 ) | | | | +-------- month ( 1 - 12 ) | | | | | +----- day of week ( 0 - 6 ) ( Sunday = 0 or 7 ) | | | | | | +-- year [ optional ] | | | | | | | * * * * * * * command to be executed      Examples.   1. For every 10 seconds    0/10 * * 1/1 * ?     2. For every Sunday midnight at 23:00...

1. Modularization Do not write the whole logic code in one block/function instead delegate the each and individual responsibility to each function. For example if you are converting one Date time format to another write this logic in Utils and use it. It might be useful in other place as well. And if you come across any common piece which is repeated in you logic put it in a function call where ever needed. This is basic fundamental rule. 2. Single Responsibility. Always delegate single responsibility to one block/function of code. Don't mess multiple operations in a single block/function. And make sure block/function of name should ideally match to what it actually does . 3. Name Justification Always declare the class, method or variable names based on its purpose. And don't use any shorter names. The one who reads your code should get idea what actually it does.

Jax RS API and its implementation Clarification The API does not provide any implementation code (concrete classes that do the actual processing). The API only specifies interfaces, annotations, exceptions. There can be concrete classes with some very basic, core behavior. The idea of standard APIs, like JAX-RS, is to give developers something to code against regardless of the underlying platform and implementation. Jersey, RestEasy and CXF are the implementations - it includes many concrete classes that actually handle the business  promised  by the API according to JSR  (Java Specification Request) 311. In JAX-RS case - it handles requests and responses. Apache CXF - CXF is the implementation from Apache Group. Jersey - the JAX-RS Reference Implementation from Sun. We're using Jersey as its packed full of features (e.g. WADL, implicit views, XML/JSON/Atom support) has a large and vibrant developer community behind it and has great spring integration...

1. With Spring Boot you can focus more on business features and less on infrastructure. 2. With Spring Boot, project gets added with required libraries and configurations based on reasonable assumptions that Spring boot makes. Assumptions will be made based on the class path. 3. Spring Boot doesn’t generate code or make edits to your files. Instead, when you start up your application, Spring Boot dynamically wires up beans and settings and applies them to your application context.  Spring Boot = Spring Framework + Embded HTTP Servers (Tomcat, Jetty etc..) - XM Configurations For more information visit http://projects.spring.io/spring-boot/

JDK = JRE + Java Development tools JRE = JVM + Java inbuilt packages + Run time libraries Most of the people always has the doubt of why JDK is again having JRE inside ? Though it got pro vided out of the JDK. Standard JRE doesn't have tools like javac, javaDB and tool.jar So make sure you always point JDK JRE in your project build path. Except the above difference rest of the things are same with Standard JRE's and JRE inside JDK.