Java EE 7 is now an immense step up in productivity from the J2EE 1.4 specification, yet there are many businesses out there still reliant on source code with legacy practices. Java EE 7 strongly leans on the annotations, therefore we recommend your business upgrades their Java SE environment to at least JDK 7. In February 2013, Oracle Java SE 6 declared End-of-Life of public releases (http://www.oracle.com/technetwork/java/eol-135779.html).
The serious actual effort of upgrading J2EE to Java EE is proportional to the number of lines in your application, whether it is based at all Java SE 5 or better, using generics, enumerations, and annotations. It depends on the interaction complexity in your existing software. The task can be straightforward, lasting several careful, agile development iterations, but it equally can be very tough to upgrade your software. Upgrading from J2EE in the future is set to get even harder, especially when the next standard, which is aimed at Moving to the Cloud, comes aboard. Our advice is simply to upgrade sooner rather than later.
Here are a few tips to help the architectural team along with this upgrade:
@java.ejb.Stateless
and @java.ejb.Stateful
. Replace singleton beans that utilize proprietary application server APIs with the standard @java.ejb.Singleton
beans.@javax.annotation.Inject
and replace those older JNDI lookup service codes. Prefer Resource Injection for database connections, JMS destinations, and concurrency executors with @Resource
injection.@Asynchronous
methods in EJB.These tips should help you get over the curve to a fully working, tested, and ingrained Java EE 7 application. Only then should your architects decide on approaching new features: CDI, JAX-RS, and WebSocket.
CORBA and Object Request Broker is a technology designed in the late 1990s into the millennium, which provided inter process communication over distributed systems. This standard of communication is still maintained by the Object Management Group. IIOP systems can be implemented in any language such as Java, C++, or C#. RMI is the Java implementation over this protocol.
The full specification of Java EE 7 permits the removal requirement for supporting EJB. CMP (Container Managed Persistence), BMP (Bean Managed Persistence), JAX-RPC, deployment API instead are made optional. Support, therefore, for CORBA, is now optional for application server products.
The following table lists the other older technologies that are supported or are optional in the Java EE 7 standard:
3.12.136.119