New Features in Java Enterprise Edition 6 (JEE 6)

Latest version of Java Enterprise Edition is focused on eae of development and simplicity. Key goals of this version are

  • Extensibility – supports for additional technologies and frameworks
  • Profiles – support for creating custom profiles based on application scope or requirement.
  • Pruning

New Features introduced in this edition are

  • Simplified EJB 3.1
    • No local business interface – one step further from EJB 3.0 specification, EJB 3.1 specifications removes mandatory business interface
    • Singleton EJB – to share application wide data and support concurrent access.
    • EJB 3.1 can be part of war file directly without creating a separate jar file

EAR >>
      WAR >>
            JSP/Static Pages
            WEB_INF >>
                  web.xml
              lib >>
              classes >>
                         Servlet and Other classes
                         EJB1
                         EJB2
             ejb-jar.xml

    • Embeddable API for executing EJB in Java SE environment: The idea behind this feature is to allow EJBs to run in Java SE environments
    • Asynchronous Session Bean: A session bean can support asynchronous method invocations.
    • EJB Lite

 

  • Servlet 3.0 – some of the major changes in  Servlet 3.0 are
    • Annotation support
    • Web Fragment – Logical partitioning of web.xml so different embedded framework  such as  Structs and  JavaServer Faces
    • Support for Asynchronous processing  to support AJAX.

  • JAX-RS 1.1 – API for RESTful web services . It supports  annotation based development.

  • JCDI – support for injecting lifecycle component , dependencies.

 

Comments

Post a Comment

Popular posts from this blog

State Design Pattern by Example

Image
State pattern falls under the category of Behavioral patterns. State design pattern comes in picture when a system’s behavior is depends on its own state or some other resource’s state. If an implementation is depends on the states, we end up with snarl of conditional statement every where in code. A very neat approach to deal with such situation is to separate out every state’s behavior and use them where ever they are applicable. The state pattern allows an object to alter its behavior when is internal state changes . The object is appeared to change its class. State pattern is a way to implement the same. Class Diagram : As above class diagram shows, System class holds state instance. As state of system changes , all handle request delegated to respective State’s concrete implementation. Example : Have an example of Vending machine. Vending machine has following states No Coin Inserted Coin Inserted Dispensing Empty Following diagram explain behavior...
Read more

Eclipse command framework core expression: Property tester

Image
Addition to Eclipse command framework series, this post explains use of property tester to control command’s enable/visible properties. In earlier post we have tried declarative way to achieve same thing but property tester gives us more control. Property tester is associated with, tester class which implements PropertyTester.java, a namespace and set of property which it supports. We can refer this property tester using its namespace + a property name. It gives you call back to test() method with property name as parameter inside property tester class. We can configure property tester for type of input parameter. Here is sample declaration of property tester extension point < extension point ="org.eclipse.core.expressions.propertyTesters" > < propertyTester class ="com.example.advance.cmd.EditorTester" id ="com.example.advance.cmd.propertyTester1" namespace ="com.example.advance.cm...
Read more

Composite Design Pattern by example

Image
This post explains Composite design pattern with an example. When to use ? – Use Composite pattern when you have treat a collection of objects as they were once one thing. With Composite design pattern it is very easy to simplify operations over collection data structure. It reduces complexity of the code required if you were going to handle collection as special case. How to Use? - The Composite pattern consist of Component, Leaf and Composite Classes as shown below class diagram Component – Component declares the common interface that both the single and composite nodes will implements Leaf – The leaf class represent the singular atomic data type implementing he component interface.     Composite – Composite is an abstract entity which declares common functionality which are needed by concrete implementation for handling collection data. An Example -   Item.java public interface Item {     public double getPrice(); ...
Read more