Why the next Galaxy Nexus must have quad-core CPU

I know there are a ton of rumors going around (oddly identical) that the new Nexus phone will be just a tad better than the Galaxy Nexus (slightly better processor: dual-core 1.5 Ghz, memory card support, better camera: 8Mp and an extra "HD" added to the display). And I think we can all agree that this is a pretty lousy update. But is this what Google really has planned? I mean, the Nexus 7 just came out, it's cheap (about $200) and most importantly it's quad-core. So wouldn't it make sense for the new Nexus phone to have at least a quad-core CPU? if not cheap as well?

Also, since I've reached this point, I would have to say that upon further thinking, the best decision (Android-phone-purchasing-wise) would probably be to wait out until the next Nexus phone with a quad-core, because that is pretty much the top of the hardware upgrades (sure they, can add more RAM and better memory but it won't make much of a difference). And if you reached the top of the hardware that means that future upgrades will mostly be software-based (which since you're buying a Google phone) you're pretty much set up. 

So my recommendation is to wait until the next Nexus with quad-core. (I hope I'll make it..) 

Why the best Android phone is Galaxy Nexus (and should I buy it?)

If you stop to think about it, the best Android phone.. should (I think) deliver the best Android experience. I am right? I mean, right now, I don't have the best Android phone (not even close) and it looks like I'm not going to see Gingerbread :) (except for custom ROMs, but that's another post). So what I would want from a nice Android phone is to get all Android updates, I mean ... I don't want to be greedy but at least Apple-like support (the next 3 OS upgrades or so). Now that is my ideal Android phone; and let's face it, the only way to get that is buying Google's phone: The Galaxy Nexus (in this case). I mean, sure it isn't the fastest candidate on the market, but are you going to be happy with a One X or S3 that after Jelly Bean might be left out staring at the sun? I know I won't. 

But still.. I hope it's not getting too slow.

Some people agree, at least this guy does. Should I buy it?

Forcing TaskRejectedException in Spring

Suppose (for testing purposes) you want to force a TaskRejectedException when using Spring Integration channels. All you have to do is

• send a reasonable number of objects to the channel (let's say a minimum of 5)
• configure your queue capacity to .. 0
• and (important) set the thread-pool size to (as low as you can) 1

I'm using a task executor in this example:

id="someExecutor" keep-alive="120" pool-size="1" queue-capacity="0"

Good luck