It looks like it's just a straight toString result as generated when a class doesn't override toString with it's own implementation.
If that's the case (which you can check by overriding toString and seeing if you get a different output), then according to the Java documentation for Object (http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Object.html) the default implementation for toString is:
getClass().getName() + '@' + Integer.toHexString(hashCode())
Hashcodes -- what the number you're referring to -- are pretty tricky. Again, from the Java documentation on Object, hashcode is implemented with the following contract:
The general contract of hashCode is:
* Whenever it is invoked on the same object more than once during an execution of a Java application, the hashCode method must consistently return the same integer, provided no information used in equals comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application.
* If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result.
* It is not required that if two objects are unequal according to the equals(java.lang.Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hashtables.
So, short answer, you the number doesn't mean it's the same object reference. They may have the same values stored, but even that's not a given.