Comments for eknori.de

Comment on org.apache.commons.collections – MultiValueMap by axel

axel — Tue, 22 May 2012 07:57:44 +0000

They say that guava from google is a tad “better” alternative for jakarta commons this days. Personally, I haven’t find much use for the jakarta commons except StringUtils in my projects.
You get this multivalue feature with a simple method like this:

private void addMultivalue(Map map, String key, String value) {
if ((map==null) ||(key == null) || (value == null)) throw new IllegalArgumentException(“None of this arguments should be null: map=” + map + “, key=” + key + “, value=” + value);
Set values = map.get(key);
if (values == null) {
values = new HashSet();
values.put(value);
map.put(key, values);
} else {
values.add(value);
}

}

Sometimes its questionable if its really worth to add a new 3rd party lib. Well, I allways try to convince people to add this, though: http://commons.apache.org/lang/api-2.5/org/apache/commons/lang/StringUtils.html

Comment on org.apache.commons.collections – MultiValueMap by Ulrich Krause

Ulrich Krause — Mon, 21 May 2012 04:28:48 +0000

Absolutely true, you can put an object into a map etc.
The advantage of the MultiMap ( to me ) is that you do not have to care about the logic of how to add the values to the map.
Using the MultiMap is a more intuitive way to do this. Adding to a map is map.put(key, object) and so is multimap.put(key, object).
Without the multiMap you would have to check, if the key already exists and then add another object to an ( existing ) object for this key. Code, you would have to write by yourself.

Comment on org.apache.commons.collections – MultiValueMap by David Leedy

David Leedy — Mon, 21 May 2012 01:54:11 +0000

Looks interesting but maybe I’m missing something. Can’t you put an object into a map? Tree or hash? As the value? So an array or custom object that could hold multiple values? I thought so at least. That could give you your multi values I’d think.
But it is late here….

Comment on Joda to the rescue by Mikkel Flindt Heisterberg

Mikkel Flindt Heisterberg — Sat, 12 May 2012 07:27:35 +0000

The date represented by java.util.Date is always the UTC date and hence daylight savings doesn’t apply. Daylight savings and time zones is what the java.util.Calendar is for why this is a perfectly fine approach. Of course the date objects would come from a daylight savings/time zone aware piece of code in a real piece of code where Locale etc. apply.

Comment on Joda to the rescue by Stephen Colebourne

Stephen Colebourne — Fri, 11 May 2012 11:30:18 +0000

As a general rule, LocalDate should be preferred to DateMidnight for cases like this. Thats because in some time-zones, midnight does not occur on the date of daylight savings change – ie. time jumps from 00:00 to 01:00 with midnight never occurring. DateMidnight clearly has issues with this. LocalDate does not have a time-zone and so handles it fine.

Mikkel, your code ignores daylight savings time days that last 23 or 25 hours. More generally, its only really reliable if your default time-zone is UTC. If thats fine in your case, great, but please don’t pretend that the code is equivalent.

Comment on Joda to the rescue by Ulrich Krause

Ulrich Krause — Fri, 11 May 2012 05:49:04 +0000

Thx for sharing, Mikkel. Much easier, indeed …

Comment on Joda to the rescue by Mikkel Flindt Heisterberg

Mikkel Flindt Heisterberg — Thu, 10 May 2012 17:58:55 +0000

While Joda Time is a great library there is an easier way to accomplish what you are trying to do. Simpy remove the time component by doing a simple modulus calculation. I am not trying to be smart about it but we do this quite a lot at OnTime Code could look like so:

Date d = new Date();
long lngTime = d.getTime();
lngTime -= lngTime % TimeUnit.DAYS.toMillis(1);
Date dNoTime = new Date(lngTime);

The latter date object creation isn’t actually necessary for the comparison. An utility function could be like so:

private boolean isSameDay(Date d1, Date d2) {
long lngTime1 = d1.getTime();
lngTime1 -= lngTime1 % TimeUnit.DAYS.toMillis(1);

long lngTime2 = d2.getTime();
lngTime2 -= lngTime2 % TimeUnit.DAYS.toMillis(1);

return lngTime1 == lngTime2;
}

Hope it helps and it helps remove the dependency on Joda Time if that’s all you’re using it for.

Comment on SSJS – @CancelPartialRefresh by Stephan H. Wissel

Stephan H. Wissel — Wed, 09 May 2012 05:03:04 +0000

Sweet. Keep the @ rolling

Comment on Access UserBean from Java by Mark Leusink

Mark Leusink — Tue, 08 May 2012 17:45:44 +0000

Did you also check the source code for the UserBean? It is in the ExtLib download. The get() function is actually pretty handy and you might want to add that to every bean you create to be able to access it in Java:

public static final String BEAN_NAME = “userBean”; //name of the bean

public static UserBean get(FacesContext context) {
UserBean bean = (UserBean)context.getApplication().getVariableResolver().resolveVariable(context, BEAN_NAME);
return bean;
}

Comment on FollowUp: Paul Withers: Extending Themes – Custom Pager Labels by Real estate consultants gurgaon

Real estate consultants gurgaon — Mon, 02 Apr 2012 08:00:22 +0000

Your blog is perfect, and I like this article. I find the information I need.