JavaEE Lab 2 — Entity Bean
The configuration step should be done as for EJB Lab 1 first and the application server should have been started.
Understand the example source code
Analyse the EJB-Jakarta-3* samples.
The examples use 2 entities: a Customer and an Order, with a OneToMany relationship between them. The Customer and the Order classes are Plain Old Java Classes (POJOs).
The META-INF directory contains a persistence.xml file, where derby is indicated as default in line jdbc/__default. The application is ready to work with the Derby embedded database.
Using a Derby Database
Derby is a relational database corresponding to an implementation of the Java Persistence API (JPA), bundled with glassfish.
See the glassfish quickstart guide to discover more on the basic features of glassfish and the use of derby.
Once the glassfish application server has been started (by
asadmin start-domain domain1), you also have to start the
database server as follows:
- Compile, deploy and run the example by following the instructions in the README.txt file.
Check that the deployment took place properly and that the
application appears in the list of deployed components.
To check the content of the Derby database, you can use the
ij tool. In a terminal window, launch the
Then connect to the Derby database and write SQL requests:ij version ij 10.6 ij>ij> connect 'jdbc:derby://localhost:1527/sun-appserv-samples'; ij> select * from Customer;
Stop the Derby database server:
Documentation on the Java Persistence Query Language
First step of micro-project
Start the microproject
Develop a client-server application for implementing the first step of the micro-project.