Ramki Technical Blog

Java 7  is an upcoming major update to Java, releasing on July 28, its upgrade/add many features. Upgraded Features - Java 7 update the XML and Web Service stack to current stable build JAXP 1.4, JAXB 2.2 and JAX-WS 2.2. - Update the Nimbus Look and Feel (Next Cross Platform UI). Its already added Java 6 Update 10. check here - Translucent and shaped Windows        This feature is also included in java 6 update 10.  this features provide to create transparent and any shape window in java. for more info check this New features in java 7 Small languages changes (Project Coin Part 1) Project Coin  is one of the  project in java 7 for java language spec (JLS). Project Coin have 2 parts. the first part is add to java 7. and next part is comes with java 8 in next year (2012).  Binary literals and underscore in numeric literals                    now we can assign bina...

In this post we will see how to run multiple tomcat instances on single machine and under single user account. We first see the  tomcat directory structure. . here each folder uses following purpose. bin -  It contains all binary and script files for running tomcat. lib - contains all shared libraries used for tomcat conf - contains configuration information like which port tomcat can bind , etc... logs - it contain all logging details temp - this folder tomcat used for temporary files purpose webapps - this folder is very important. here we put all application war files. work - If application contain any jsp then jsp is translated and converted into servlet its stores here. In when run the tomcat its uses 5 environment variables. They are  CATALINA_HOME, CATALINA_BASE, CATALINA_TMPDIR, JRE_HOME/JAVA_HOME, CLASSPATH in above list CAT...

This is Third  part of JSF 2.0 discussion. Please visit  part one   and part two Update : New Post JasperReports in JSF In this post we will discuss JSF with AJAX. In JSF 2.0 gives full support for ajax integration in web application.  With Ajax, web applications can send data to, and retrieve data from, a  server  asynchronously (in the background) without interfering with the display and behavior of the existing page. so with help of ajax we will make more interactive page.   JSF 2.0 Faclets provide <f:ajax> tag for achieve ajax in web application without writing client side java script ajax code. JSF 2.0 takes care all of this. JSF and ajax integration is one of the greatest feature. and no other framework provide this much easy ajax integration in web application. Consider we have one simple web application it prompt the name and click submit button its display the nam...

This is Second  part of JSF 2.0 discussion. Please visit   part one   Update :  New Post JasperReports in JSF In JSF 2.0 part 1   post, i used  @ManagedBean annotation for POJO java class. Its OK, actually it derived from JSF 1.2.But we should use @Named annotation instead of @ManagedBean, if CDI  ( Contexts and Dependency Injection ) environment is available. I used Tomcat 7, its not Java EE 6 server and by default CDI is not available.  But we can use JBoss's Weld lib for achieve  CDI in tomcat with minimal configuration. Weld is reference implementation of CDI and its comes standalone version also. This standalone version weld provide CDI environment for both Web Application and Java SE application. By default Glassfish 3.0/3.1 server comes with weld  library for CDI Environment. Here i am using Glassfish server with CDI enabled. Page Navigation ...

Contexts and Dependency Injection (CDI )  JSR 299  is a new feature in Java EE 6 Web Profile .  Its Enhance the JSR 330 Dependency Injection in Java. CDI are highly used annotation. CDI makes Loose coupling between classes. To use javax.inject.Inject annotation, we can inject any class into another classes  i put 4 part series of CDI, you can get it here Learning CDI (Contexts and Dependency Injection) Part 1 Learning CDI (Contexts and Dependency Injection) Part 2 Learning CDI (Contexts and Dependency Injection) Part 3 Learning CDI (Contexts and Dependency Injection) Part 4

Java Server Faces (JSF) is one of the presentation web frameworks in java. There is lots of others frameworks like Spring, GWT, Wickets, Struts. Today this post we ll discuss why JSF is more important then others.Here I am not  criticize any frameworks. i just talking about JSF.   In JSF 1.2 and previous version of JSF used JSP as a view declarative language and JSP life cycle is not matched with JSF and ajax requests. JSF 1.2 are complex to use and they have some short coming in feature. But JSF 2 is completely changed the adapt lots of technologies, but still its support backward compatible.Its very easy to learn. More over JSF is center piece in Java EE 6 Spec. It means that what are the new components or specification introduced in Java EE 6 are seamlessly integrated into JSF. Because those components spec is designed for JSF in mind.

Update : I put new post for  Why should I learn JSF                   I put new post for  Understanding Java Server Faces 2.0  Part  2   JavaServer Faces (JSF) is a Java-based Web application framework intended to simplify development integration of web-based user interfaces.  Java Server Faces (JSF) 2.0 is a improved component of Java EE 6 Specification.  Its Component based model. Its is alternative technology for Struts, JSP, Spring. Its MVC (Model-View-Controller) based architecture.

This is Fourth  part of CDI discussion.Please visit   part one ,  part two  and    part three Interceptors Interceptors is one feature of CDI. Using this feature we can intercept the method call. Its counterpart technique for Aspect Oriented Programming (AOP) in Spring. Its helps to analysis the business methods and these interceptors are disabled by default. so we can enable/disable the interceptor in deployment time through beans.xml  file. Create interceptor      To create interceptor involves two step process. first to create interceptor binding and  implement the interceptors. here we create Log Interceptor, so we need to create Log Interceptor Binding(its  like qualifier) Log.java here @InterceptorBinding is represent that the annotation 'Log' is interceptor second, we need to implement the interceptors LogImpl.java here @Interceptor represent that it...

This is Third  part of CDI discussion.Please visit   first part  and part two , @Alternative In part two  we seen @qualifier 's to resolve the unambiguous problem for one interface and more than on implementation. In qualifier helps to solve in development time. (i.e all meta information is stored in class files). Another solution is @Alternative annotation solve the problem in  deployment  time. all configuration is stored in beans.xml in WEB-INF folder We take same example what we discussed in last part  one interface (Hello) and two implementation(HelloImplOne, HelloImplTwo) here i marked @Alternative in both implementation Hello Interface HelloImplOne Implementation HelloImplTwo Implementation and go and modify the beans.xml in WEB_INF folder In <alternatives> tag in beans.xml we need specify which one need to inject. See the screen cast for demo...