doobries domain

Now that JBoss AS 6.0 has been released with full support for the Java EE 6 Web Profile, lets take a quick look at some of the new features of EJB 3.1 that are available. Three of the main features of EJB 3.1 are: EJB’s can be deployed as part of a WAR file and do not need to be is a separate EJB JAR file. EJB’s can be developed with no business interface. EJB’s can be deployed as Singletons. Let’s take a look at each of these in turn. 1. EJB’s can be deployed as part of a WAR file. Not much to look at here I’m afraid! The thing to notice is that now with NetBeans (I’m using NB 7 Beta), you can create a simple Java EE 6 Web Project and create EJB’s within the web project. If you are developing a web project, there is no longer any need for an additional JAR to deploy any EJB’s that you use. 2. EJB’s can be developed with no Business Interface Creating an EJB without a Business Interface is as simple as creating a POJO, which in fact the EJB is! In it’s simplest form,...

In case you missed the announcement last week, JBoss AS 6.0 has been released for General Availability. JBoss AS 6.0 provides an fully certified implementation of the Java EE 6 Web Profile Specification ( JSR-316 ). So, what does this give to Java EE developers exactly? JBoss AS 6.0 is the latest in the line of community supported Java EE application servers. From the first milestone release to the final release of AS 6 has taken nearly a year of development and testing. JBoss AS is easy to install (simply unzip it) and run requiring only a compatible JDK to run. Configuration and management of JBoss AS can be done either via the excellent web based Administration Console , via XML file manipulation (this is particularly useful for integration with Maven or Ant) or via the command line Twiddle tool. The Java EE Web Profile was designed to provide developers with all the tools that they need to build Rich Internet Applications. The Web Profile Specification describes the profile ...