A couple of comments. Hashtable is useful when you need to have synchronized access to the elements in a Map, if that's not the case HashMap is preferred.
In Java we don't have "pointers", but surely we have references to objects (please remember that in Java all objects are passed by value, not by reference). And yes, you can store references to objects as values in a Map. I think you're confusing concepts from C/C++ with concepts in Java, maybe you should explain exactly what do you want to do with the "pointers".
Just to be sure - you can have a Map such as this one in Java:
Map<Integer, Integer> table = new HashMap<Integer, Integer>();
In the above code, the keys and values of the Map are references to Integer objects, and the Integer class is immutable, meaning that you can't change its value once it's in place - but of course, you can change the value pointed to by a key in the Map.
EDIT :
The sample in the question would look like this in Java:
Map<Integer, Integer> ht1 = new HashMap<Integer, Integer>();
ht1.put(1, 100);
ht1.put(2, 200);
Map<Integer, Integer> ht2 = new HashMap<Integer, Integer>();
ht2.put(1, 100);
ht2.put(2, 200);
Map<Integer, Integer> value = new HashMap<Integer, Integer>();
value.put(100, null);
value.put(200, null);
In the above code all the integers in the three maps are references to immutable objects: what appears to be the number 100 in reality is a reference to the object new Integer(100), and because Integer is an immutable class, it's possible that all three references to new Integer(100) point to exactly the same object in memory.
So, answering your question: yes it's possible in Java to store a pointer in ht1 and ht2 instead of 100 and 200, which points (and can access) to 100 and 200 of value hashtable. In fact that's what is happening already, and there's no other way to do it - because maps in Java can not store primitive types (like int), only references. And again, given that all instances of Integer are immutable, you can not change their value, because doing so would change the values in the other places where they're being shared and used.