Hi Raghu and Jonathan, While App Server giants are currently competing to develop the support for EJB3, what App Server did you use to test the code while you were writing the book? Did you use the reference implementation of the spec, which is GlassFish?
Hi Ko Ko- We used Glassfish for all of our in-book and online samples, since it is, as you mention, the reference implementation. We also ran these samples with a pre-release of Oracle's iAS version 10.1.3.1, which is compliant with the final draft of EJB 3, including JPA.
The online samples all run with ant and Glassfish, but you'll notice that we also bundle the JDeveloper project and deployment files, so that you can run them with Oracle's JDeveloper once the 10.1.3.1 release becomes available. JDeveloper bundles OC4J 10.1.3.1, which is Oracle's Java EE server, so you will be able to run the samples against that server as well.
Ko Ko Naing
Joined: Jun 08, 2002
Originally posted by Jon Wetherbee: The online samples all run with ant and Glassfish, but you'll notice that we also bundle the JDeveloper project and deployment files...
Yes Jon, I've just downloaded the source code from Apree website and found out the .jws files are there in the chapter folders. Are they JDeveloper project files? Though I have experience with JBuilder(Commercial) and Eclipse(Open-source), I've never tried JDeveloper before.
Joined: Oct 05, 2006
Hi Ko Ko- Yes, the .jws (Java Work Space) files that you see can be opened in JDeveloper 10.1.3.1. We grouped the samples by book chapter, so there's one .jws file per chapter, and each WorkSpace contains one or more .jpr (Java PRoject) files.
Barring any difference between the pre-release version of JDev we built them with and the version of JDev 10.1.3.1 available on http://otn.oracle.com , you should be able to open them and run the samples. The readme.txt files guide you in building and running the samples using ant and GlassFish; we just built everything using JDeveloper, and planned to flesh out the readme.txt files to describe the JDev steps once 10.1.3.1 had been finalized.