What’s In The Gmail Magic Inbox?

One almost surefire way to find if a new feature is on the verge of launching is to dig through code. That’s exactly what led to finding a reference to something called “Magic Inbox,” in Gmail. But what is it? Well, it could just be another one of those nifty, but small new features that Google loves to roll out in Gmail Labs at breakneck speed. But there’s a chance it’s something much, much bigger.

Specifically, Google Operating System, which did the digging, believes that the feature likely is a way to sort your Gmail inbox by your social graph. The two references to “friends” in the code, seems to lend some credence to this. Presumably, this would allow you to better filter your inbox based on if you have specified the emailer as a contact. As someone who gets bombarded by email everyday, most of which is not from people I actually know, I would weep with joy if such a feature were implemented. And so would my mom, as she may actually get emails back from me were that the case.

Of course, others have been working on this same idea as well. Yahoo has been saying for a while that it wants to use your inbox as a part of your social graph. Microsoft’s Hotmail has been working on things in the area as well, as has Xobni. But given all the work Google has been doing recently to tighten up its social graph across its huge network of services, a social filter in Gmail could be very, very useful.

Users are likely to have security concerns about this as well. Some people want their email client to be completely private and not a part of the social graph. Of course, Google has already been using Gmail as a key starting point for your social graph for a while now, even if you didn’t realize it. Well over a year ago, Google it rolled out its social features to Google Reader, pulling in who it thought your friends were based on who you emailed in Gmail.

This proved to be an awful idea as people you email aren’t necessarily your friends. Google eventually rolled out several updates to this feature to allow users to better tailor their relationships. And that would obviously be a key part of a Gmail social filter as well. You need to be able to separate out your actual friends from those who you simply have contacted in the past, or maybe even correspond with a lot.

While Google hasn’t exactly nailed the social features, it’s pretty clear that the company is thinking about them — a lot. And that your Google Contacts, which started as a part of Gmail, but have since been spun out, are a key part of it.

Google I/O, its large developer conference is taking place next week. Google is likely to use the event to unveil some key new things it has been working on. Could that be a “magic inbox,” which is also called “icebox inbox” in the code? We’ll be there to find out. Maybe Gmail will even leave beta — but probably not

 Source : TechCrunch.com :Gmail Inbox

How to solve “error could not find java runtime 2 environment” while opening an IDE in windows

Many times it happen that the IDE which you are installing is not compatible with the old JDK version. And when you try to open the IDE this error pops up.

This is because the oldversion of JDK is set . There are many ways to get this correct of which the one i prefer most is as follows:

  • Open your Registory Editor by doing ‘Windows’ button + ‘R’ key
  • type regedit
  • goto :HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment\
  • Change to current value of ‘CurrentVersion’ to the desired JDK version

And open the IDE now.

Spring AOP tutorial -I


Aspect-Oriented Programming (AOP) complements Object-Oriented Programming (OOP) by providing another way of thinking about program structure. The key unit of modularity in OOP is the class, whereas in AOP the unit of modularity is the aspect. Aspects enable the modularization of concerns such as transaction management that cut across multiple types and objects.

AOP concepts:

Aspect: a modularization of a concern that cuts across multiple classes. Transaction management is a good example of a crosscutting concern in J2EE applications. In my words: a trigger which can affect the multiple classes a one point….
Join point: a point during the execution of a program, such as the execution of a method or the handling of an exception. In Spring AOP, a join point always represents a method execution. In my words: a locus of points where execution will happen.
Advice: action taken by an aspect at a particular join point. Different types of advice include “around,” “before” and “after” advice. (Advice types are discussed below.) In my words : the action to be taken at the point.
Pointcut: a predicate that matches join points. Advice is associated with a pointcut expression and runs at any join point matched by the pointcut (for example, the execution of a method with a certain name). The concept of join points as matched by pointcut expressions is central to AOP, and Spring uses the AspectJ pointcut expression language by default. In my words a criteria used to locate point.
Introduction: declaring additional methods or fields on behalf of a type. Spring AOP allows you to introduce new interfaces (and a corresponding implementation) to any advised object. For example, you could use an introduction to make a bean implement an IsModified interface, to simplify caching. (An introduction is known as an inter-type declaration in the AspectJ community.)
Target object: object being advised by one or more aspects. Also referred to as the advised object. Since Spring AOP is implemented using runtime proxies, this object will always be a proxied object.
AOP proxy: an object created by the AOP framework in order to implement the aspect contracts (advise method executions and so on). In the Spring Framework, an AOP proxy will be a JDK dynamic proxy or a CGLIB proxy.

Consider the example:

Lets declare an interface:

public interface Foo {

Foo getFoo(String fooName,int age);

void getAfter();

void getBefore(String myName);


A class implementing the interface:

public class DefaultFooService implements FooService {

public Foo getFoo(String name, int age) {

return new Foo(name, age);


public void getAfter() {}

public void getBefore(String myName) {}


Till here we have simple java implementation.
Now let see come AOP concepts in picture.
Before – Now I want that before the getBefore() method is called I want to log message saying what is the parameter passed.
After – Also I want that once any method in the interface is called a message should be logged after it.
I have a class which will be called to satisfy the above criteria.

public class SimpleProfiler {

public void afterMethod() throws Throwable {

System.out.println(“After the method call”);


public void beforeMethod(String myName){

System.out.println(“My name is “+myName);



The afterMethod() will log message after any method is called and beforeMethod() will log message before getBefore() is called.
To configure this we will used xmlThis is how I configure my spring.xml.

<beans xmlns=http://www.springframework.org/schema/beans&#8221;



xsi:schemaLocation=http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd

http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd&#8221;>

<!– this is the object that will be proxied by Spring’s AOP infrastructure –>

1 <bean id=“fooService” class=“DefaultFooService”/>


3 <!– this is the actual advice itself –>

4 <bean id=“profiler” class=“SimpleProfiler”/>


6 <aop:config>

7                <aop:aspect ref=”profiler”>

14 <aop:pointcut id=“aopafterMethod”

expression=“execution(* FooService.*(..))”/>

15 <aop:after pointcut-ref=“aopafterMethod”


16 <aop:pointcut id=“aopBefore”

expression=“execution(* FooService.getBefore(String)) and args(myName)”/>

17 <aop:before pointcut-ref=“aopBefore”





Let see how we have configure the AOP .

  • Line 1 is used to create a proxy AOP object..
  • Line 7 we define the aspect “SimpleProfiler” class which will come into picture at different point-cuts.
  • Line 6 is used to configure the AOP.
  • Line 14 defines a pointcut in which an expression needs to mention. In this case the expressions say that “call afterMethod of SimpleProfiler class for any method declared inside the FooService interface.
  • Note Line 14 doesn’t define when to call afterMethod().This is done in line 15
  • Line 15 states that call afterMethod() for id aopAfterMethod
  • Similarly for beforeMethod we define in Line 16,17.

    In above example we have

    Aspect – SimpleProfiler.class
    Point-cut – aopafterMethod,aopBefore
    Advice <aop:before> <aop:after>

    Now I am ready to run my main class and class methods of FooService.

    public class Boo {
    public static void main(final String[] args) throws Exception {
    BeanFactory ctx = new ClassPathXmlApplicationContext("spring.xml");
    FooService foo = (FooService) ctx.getBean("fooService");
    foo.getFoo("Pengo", 12);

    OutPut is
    After the method call ( log messagefor getAfter method )
    My name is Harshit (log message for getBefore)
    After the method call (log message for getAfter method)

    How to build various pointcut expression.

    IS Twitter the new business card?

    Recently a new trend is visible during tech-meet ups. While some people meeting up there were handing out business cards (mostly Moo Cards), the majority of people were merely adding the new faces they met directly to their Twitter follow lists via their smart phones. “Is Twitter the new business card?” This is how it went down:

    Person meets person

    Pleasantries are exchanged

    Small chit chat about common business interests

    Potential plans are made

    “Let me get your contact info”

    “Do you have Twitter?” (Note: this is where a business card should be exchanged)

    “Why, yes I do?”

    Both parties whip out Smart Phones and open respective Twitter clients

     Both parties type “follow newperson” into the Twitter client and submit

     “Great, nice to meet you. I will be in touch!”

    It’s a novel idea, really. I did it myself. I found it easy and I didn’t have to worry so much about sorting through a mess of business cards when I got home (no, I don’t use a scanner). But then I ran into a significant issue: “Who the heck was that guy? Why am I following this person? What was that lady’s name again?” While doing such a thing is certainly convenient, is it realistic if you want to build a solid business relationship. There’s no way to enter details about this person, unless of course you immediately @ message them and say “Nice to meet you re: xyz.” But what if it’s for a business deal or a job opportunity? You certainly don’t want to announce that to the world. I think there’s an interesting opportunity here for Twitter, in terms of monetizing. What if the company gave people an opportunity to save contact details about a person as they add others to their follow lists? Perhaps an add-on service that we can subscribe to in order to turn Twitter into a contact database of sorts. Or, some sort of LinkedIn integration would be swell, too.

    Post taken from : IS Twitter the new business card?