NanoContainer Persistence

Separate Nano-Persistence into multiple projects akin to the rework on NanoContainer.

Details

  • Type: Wish Wish
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    2

Description

Here's a proposal layout:

+---persistence

---src
+---java
  ---org
  ---nanocontainer
  ---persistence
  ---jdbc
---test
---org
---nanocontainer
---persistence
---jdbc
+---persistence-hibernate2
---src
+---java
  ---org
  ---nanocontainer
  ---persistence
  ---hibernate
  ---classic
---test
---org
---nanocontainer
---persistence
+---hibernate
  +---classic
  ---pojo
---jdbc
+---persistence-hibernate3
---src
+---java
  ---org
  ---nanocontainer
  ---persistence
  ---hibernate
  ---classic
---test
---org
---nanocontainer
---persistence
---hibernate
---pojo
+---persistence-hibernate3.2
---src
+---java
  ---org
  ---nanocontainer
  ---persistence
  ---hibernate
---test
---org
---nanocontainer
---persistence
---hibernate
---pojo
---site
---xdocs
---style

This is taken from my own directory where I've got it set up.:

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Rimov added a comment -

(Konstantin: I'm really sorry about this. I didn't see you had assigned this issue to yourself until I had it all done. I hope I didn't waste your time.)

Here's a proposed layout complete with POMs and Hibernate Annotations Support.

I did take one "risky" thing when it comes to testing. I had Hibernate use create-drop on the hsqldb databases.

The reason I did this was because recent Hibernate versions don't really compile the metadata until at the very least a SessionFactory is created, and it never enhances the classes until a write occurs.

Because of this, it seems that the constructor wrappers for Hibernate Configuration can't be truly tested until a a write to a legitimate database occurs.

If there's problems with this, let me know.

Otherwise, as soon as folks give a green light, I'm ready for checkin.

Show
Michael Rimov added a comment - (Konstantin: I'm really sorry about this. I didn't see you had assigned this issue to yourself until I had it all done. I hope I didn't waste your time.) Here's a proposed layout complete with POMs and Hibernate Annotations Support. I did take one "risky" thing when it comes to testing. I had Hibernate use create-drop on the hsqldb databases. The reason I did this was because recent Hibernate versions don't really compile the metadata until at the very least a SessionFactory is created, and it never enhances the classes until a write occurs. Because of this, it seems that the constructor wrappers for Hibernate Configuration can't be truly tested until a a write to a legitimate database occurs. If there's problems with this, let me know. Otherwise, as soon as folks give a green light, I'm ready for checkin.
Hide
Permalink
Michael Rimov added a comment -

I've updated dependencies to synchronize with pico-gems.

Standardized on cglib-nodeps

Fixed bug where Hibernate 3.2 project wasn't included in project-wide build.

Show
Michael Rimov added a comment - I've updated dependencies to synchronize with pico-gems. Standardized on cglib-nodeps Fixed bug where Hibernate 3.2 project wasn't included in project-wide build.
Hide
Permalink
Michael Rimov added a comment -

I've checked in a new version into CVS as Mauro okayed.

Let me know if there are problems with the build.

Show
Michael Rimov added a comment - I've checked in a new version into CVS as Mauro okayed. Let me know if there are problems with the build.

People

  • Assignee:
    Michael Rimov
    Reporter:
    Michael Rimov
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: