Originally posted by Michael Hildner:
Did you also change your primary key class? Is is the same name? Is the name correct in the deployment descriptor?
Dear Michael problem is not the one that understand. These are the events sequence
Lookup the bean with JNDI name (Successful)
Creating the bean with a primary key(cosposite) (Successful)
Change one of the fields of the primary key e.g primary key is ID and Name and I created the bean with ('10','Adeel') later I change name from Adeel to 'Nayyer' by calling bean method changeName(String name); this change also reflects in my database so that means the changing is successful. after that if I go to execute any method on the same bean previously created it throws the exception which mention that server is trying to find out the bean with the same old ID and name.
Now I want to know that does ejb specification discuss this problem and its solution.
and what should I do to over come this problem.