Home/ Questions/Q 586589
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T15:07:23+00:00

My entities currently contain java Date properties. I’m starting to use Joda Time for

  • 0

My entities currently contain java Date properties. I’m starting to use Joda Time for date manipulation and calculations quite frequently. This means that I’m constantly having to convert my Dates into Joda DateTime objects and back again.

So I was wondering, is there any reason I shouldn’t just change my entities to store Joda DateTime objects instead of Java Date objects?

Please note that these entities are persisted via Hibernate. I found the jodatime-hibernate project, but I also was reading on the Joda mailing list that it wasn’t compatible with newer versions of hibernate. And it seems like it isn’t very well maintained.

So I’m wondering if it would be best to just continue converting between Date and DateTime, or if it would be wise to start persisting DateTime objects. My concern is being reliant on a poorly maintained library.

Edit: Note that one of my objectives is to be better able to store timezone information. Storing just a Date appears to save the date in the local timezone. As my application can be used globally, I need to know the timezone as well. Joda Time Hibernate seems to address this as well in the user guide.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think using the Joda DateTime as your bean property type is probably a good idea. You can then have Hibernate do the conversion and save the property as the native database date format.

    I have personally used jodatime-hibernate and have not had a problem with it (we’re using Hibernate 3.2.5GA).

    If you have concerns about jodatime-hibernate, you can always use Hibernate’s custom type mapping mechanism (which I’m sure is all jodatime-hibernate does).

    • 0