Task #93 (closed)
Opened 18 years ago
Closed 18 years ago
Example for migrating from *.hbm.xml to JPA
Reported by: | sfrank | Owned by: | sfrank |
---|---|---|---|
Priority: | minor | Milestone: | 3.0-M3 |
Component: | Deployment | Version: | 3.0-M1 |
Keywords: | ejb3, jpa, hibernate, build, story96, iteration4 | 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).
Change History (7)
comment:1 Changed 18 years ago by sfrank
- Description modified (diff)
comment:2 Changed 18 years ago by jmoore
- Keywords story96 added
- Type changed from User Story to Task
comment:3 Changed 18 years ago by jmoore
- Keywords iteration4 added
- Milestone changed from cycle3 to cycle1
comment:4 Changed 18 years ago by jmoore
- Keywords changed from ejb3, jpa, hibernate, build, story96,iteration4 to ejb3, jpa, hibernate, build, story96, iteration4
comment:5 Changed 18 years ago by jmoore
Looking at the DSL, it seems like the following subgraph will cover all our possible types:
- Experimenter->GroupExperimenterMap->ExperimenterGroup
- Image->Pixels->Channel
As discussed in Mainz, if you can get those, Stefan, then I should be able to start updating the Velocity templates. We can try to get back to where we are currently (i.e. still using the mapping files) but with the new Java5 classes. (See #154). If that works, we can switch to JPA once testing is ready (See #95)
comment:6 Changed 18 years ago by sfrank
- Milestone changed from 3.0-M2 to 3.0-M3
comment:7 Changed 18 years ago by sfrank
- Resolution set to fixed
- Status changed from new to closed
I'll close this task now: The provided example contains a spring-configuration using an embedded hsql-database and testcases for the annotations of Experimenter->GroupExperimenterMap?->ExperimenterGroup?, Image->Pixels->Channel. If there are any errors to this example, add a new ticket and link to this story.
Adding to #96 as a task.