Difference between revisions of "EclipseLink/Examples/MySports"
|Line 69:||Line 69:|
| A team
| A team .
| A player is
| A player is .
Revision as of 10:52, 17 June 2011
EclipseLink MySports Example
The MySports example is a simple web application which demonstrates several key features of
- EclipseLink JPA
- Extensible entities with @VirtualAccessMethods
The example includes 3 projects
- MySports: A Dynamic Web project which deploys the primary application exposing a JSF and
JAX-RS (REST) front end.
- MySports Admin:
- MySports Tests: A Java project containing Junit tests that verify the functionality of
Install & Config
At present the example is only available through SVN access. When completed a ZIP download will be made available.
- Prepare Prerequisites:
- GlassFish 3.1
- Eclipse Java EE with GlassFish adapter
- Configure Eclipse
- Requires a variable named 'eclispelink_2.3_jar' for the javaagent usage of the test project
- Ensure you have a GlassFish Server configured in the Java EE perspective
- Configure GlassFish
- EclipseLink 2.3 bundles installed in GlassFish
- A connection pool named 'jdbc/MySports' must be defined in the server
- Get the example's projects
- Import the projects
- Customize the eclipselink-examples-mysports.properties file for your database
- Run The example
- Run the MySports AllTests launch target. This will create the database tables and prepare an initial population
- Run the MySports Admin application
- Run the MySports application
The domain model is that of any arbitrary sports league. The idea is that this SaaS
solution allows any league to host its information on the site and customize the data
stored as well as the look and feel.
|Division||A league contains one or more divisions of teams used to divide teams by age, skill or simply to manage a larger set of teams.|
|Team||A team belongs to a division and has a name and players.|
|Player||A player represents a person within a specified team. A player is an extensible entity type.|
The persistence layer is the main purpose of this example application. The persistence layer makes use of application bootstrapped persistence contexts with support for an EntityManagerFactory and backing ServerSession (with Cache) per league (tenant). This all bootstrapped off of a single persistence-unit definition.