Businesscalendar is really very useful, so we don't need to do that when dealing with tough customers.
I was shocked, but today I found a bug and thought it was my own problem. Later I had
To JUnit:
Public void testyhb () throws exception {
Calendar calendar = businesscalendar. getcalendar ();
Calendar. Set (calendar. Year, 2005 );
Calendar. Set (calendar. Month, calendar. yml );
Calendar. Set (calendar. day_of_month, 4 );
Calendar. Set (calendar. hour_of_day, 11 );
Calendar. Set (calendar. Minute, 35 );
Calendar. Set (calendar. Second, 0 );
Calendar. Set (calendar. millisecond, 0 );
Date date1 = calendar. gettime ();
System. Out. println (date1 );
Date date2 =
Businesscalendar. Add (date1, new duration ("2 Business Hours "));
System. Out. println (date2 );
}
Run one:
20:26:30, 046 [main] info jbpmconfiguration: Using jbpm configuration resource 'jbpm. cfg. xml'
20:26:30, 187 [main] Debug jbpmconfiguration: Creating jbpm configuration from input stream
Mon Apr 04 11:35:00 CST 2005
Tue APR 05 10:35:00 CST 2005
The difference is the big one. Look at the clover. jar next to it. Well, the clover cannot handle this.