Java Clarifications..help needed

Hi Ranchers,
I had few clarification in Core Java .Please help me out.

1>
what is shallow copy and deep copy of objects ?Please provide me an example for the same?


2>
How is HashMap and HashTable different in terms of Synchronization.?Please explain me with a real time scenario as to when i should use a HashMap and when i should use a HashTable? Real time Examples provided will be helpful to understand the differences.


3>

I have the below code class Test{ @DummyMethod Parameters are below @ClassName=Test @MethodName=DeepakLalMethod DummyMethod(String ClassName,String MethodName){ [B]//The requirement here is to invoke Method: DeepakLalMethod based on // Class: Test using Reflection API[/B]. how do i achieve it using Reflection API ?? } DeepakLalMethod(){ System.out.println("HELLO DEEPAK"); } } Please help me to solve this.? help provided will be highly appreciated.? [B] 4> Is Synchronization an overhead ? if so,why ?? [/B] Help provided will be highly appreciated -- Deepak Lal

For the answer of your first question see this link.

https://coderanch.com/t/401249/java/java/difference-between-deep-copy-shallow

Originally posted by Himanshu Gupta:
For the answer of your first question see this link. . . .

For the answer to your second question see this link. Link And this one, this one, this one and this one.

Question 2: How is HashMap and HashTable different in terms of Synchronization.?Please explain me with a real time scenario as to when i should use a HashMap and when i should use a HashTable? Real time Examples provided will be helpful to understand the differences.??

@Campbell Ricthiee :you have given me links to the API,i had enough of API information,but can you give me some real time scenario where we can implement HashMap and HashTable,Please explain me with a real time scenario as to when i should use a HashMap and when i should use a HashTable? Real time Examples provided will be helpful to understand the differences.

Please help me out with Question 3 and Question 4 as well.

Help provided will be highly appreciated.

;-)

--
Deepak Lal

2: Map example. Always use HashMap. Look in its API for what to do if you need to synhronise it.
3: Sorry I didn't notice that question. Reflection
4: Yes. Because it requires more work.

And you are going to have to get used to reading API documentation.

How to synchronize the HashMap?
Use the built-in method.

Collections.synchronizedMap(HashMap instance)
Regards.

Real-time examples of HashMap & HashTable.
Basically there is no major difference between HashMap & HashTable now.
In earlier versions HashTable is synchronized in-built that's why they preferred it.
But now you can make your HashMap synchronized by the built-in methods of Collections class.

Suppose you want to create a telephone directory where you need two entities:
name & no.
Have the name as the key & no as the value

class PhoneBook extends HashMap { public static void main(String[] args) { PhoneBook phonebook=new phonebook(); phonebook.put("sai",9916845628); phonebook.put("jothish",99876688); //to get data from hashmap System.out.println("Sai's no is : "+phonebook.get("sai"); //to make it synchronized. Collections.synchronizedMap(phonebook);
Is this suffice?
Regards.
[ December 11, 2008: Message edited by: ramya narayanan ]

Hi Ramya,
Thanks for your valuable inputs,i have agreed to whatever you say ,i have another set of questions now for you

Question 1> Understood from others.

Question 2> when do i need to use a HashMap and when do i need to use a Hashtable(Synchronized).I mean under what circumstances should i prefer a HashMap over a Hashtable and vice versa and Why? Can you give me a Real TIME SCENARIO under which you can strongly recommed me to use a HashMap and Hashtable.I need real time examples.i have understood the differences.<<Please read my question again carefully>>.?? i hope the question is clear now.

Question 3> Can you explain how to achieve it using Reflection API,how do i invoke a method using Reflection API.??SEE question 3 in the Original Post.

Question 4> Please give me the reason as to why Synchronization is an Overhead.?

Help provided will be immensely appreciated.
Please rancers share your valuable expertise and inputs.




--
Deepak Lal

Question 2> when do i need to use a HashMap and when do i need to use a Hashtable(Synchronized).I mean under what circumstances should i prefer a HashMap over a Hashtable and vice versa and Why? Can you give me a Real TIME SCENARIO under which you can strongly recommed me to use a HashMap and Hashtable.I need real time examples.i have understood the differences.<<Please read my question again carefully>>.?? i hope the question is clear now.

Please see my above post.

Question 3> Can you explain how to achieve it using Reflection API,how do i invoke a method using Reflection API.??SEE question 3 in the Original Post.

Test t=new Test(); Method m = t.getClass().getMethod("DeepakLalMethod", null); m.setAccessible(true); m.invoke(t, null);

4> Is Synchronization an overhead ? if so,why ??

As gurus said it is an overhead, but I don't know why?
But let us see.
Regards.

Hi Ramya,

Thanks for your valuable input,If you could explain the Question 4> in concern it would be highly appreciated.



--
Deepak Lal

why can't you google & post your opinions on that?
We Ranchers already have given you 3 answers straight forward which our guru campbell won't accept at any cost.
So expecting for your post on that?
Regards.

The answer to "when to use a Hashtable" is never. Never use it in new code.

Note that despite its common use to the contrary in Indian English, "real time" does not mean "practical" or "realistic". It's a technical term describing computing with hard time limits. The phrase you want is real life. You want "real life" examples. Asking for "real time" examples sounds very strange to many readers of this forum.

Regarding synchronisation overhead associated with it
Go through this link:
Synchronisation overhead
Don't forget to post what have you got from it so that it can benefit others.
Regards.

Hi Ramya and ALL
Thanks all for your valuable input,
The link which you provided simply speaks about Lock on a object.Hence being thread safe is a costly operation.So Synchronization is a costly operation.hence Only one thread acquires the lock on a piece of code hence synchronization comes in picture,which prevents multiple threads from accessing a single block of piece of code at the same time.

Please correct me IF im wrong at my statement made above.

;-)

--
Deepak Lal

off to the intermediate forum