User Story #93 (new)
Opened 18 years ago
Last modified 18 years ago
Example for migrating from *.hbm.xml to JPA — at Version 1
| Reported by: | sfrank | Owned by: | sfrank |
|---|---|---|---|
| Priority: | minor | Milestone: | cycle3 |
| Component: | Deployment | Version: | 3.0-M1 |
| Keywords: | ejb3, jpa, hibernate, build | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by sfrank)
Now that the Java EE5 has been finalised and the reference-implementation is available (Java EE Downloads), it is safe to start with migrating from the old *.hbm.xml of mapping persistence to the new annotation-based style of ejb3. (Note, that we also removed the requirement to have 1.4-client, which formerly had prevented the use of annotations on classes that ship to the client).
This process will eliminate lots of generated files and therefore will streamline the build and produce more readable files.
Goal of this story is to provide an example, how these mappings will look like to get a feel for what we have to change in the code-generation to produce ejb3-style-beans.
A lemma of this task is to ensure testability for the ejb3-style-beans (which means getting a standalone persistence-manager).
Start with Image as example, as this task is also needed for the search (see #94).
This story is part of the greater story to get a streamlined process from modelling over code-generation up to deployment (enter tasknumber here).
