Hello guys!
I stumbled over an existing issue that LocalDateTime can't traverse EJB
calls (some information is lost).
I found the following thread on the mailing list:
http://joda-interest.219941.n2.nabble.com/LocalDateTime-not-able-to-traverse-EJB-calls-td5589383.html,
which is the same problem (but already 3 years old).
I'm using Joda Time 2.3 and the issue still exists. Are there any plans to
fix it? Or can somebody point me in the correct direction to fix it? It's
not (really) feasible for me to replace all LocalDateTime instances with
DateTime instances (and I don't know the consequences of doing so).
Currently LocalDateTime looses the following information:
Inside iChronology (an instance of org.joda.time.chrono.ISOChronology) :
- iDayOfWeek
- iDayOfMonth
- iDayOfYear
- iWeekOfWeekyear
Unfortunately this will render the LocalDateTime instance useless as many
methods will throw a NullPointerException.
One (possible) workaround I've discovered would be the following:
public LocalDateTime getSomeDate() {
return new LocalDateTime(someDate.getLocalMillis());
}
So even if someDate is "corrupted", it will return a "properly initialized"
date. But this is far away from a good solution..
Any help is very much appreciated
Kind Regards
Matthias
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
Joda-interest mailing list
Joda-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/joda-interest
