Dear Amit,
           i could not understand why u want to give set and get methods 
for your primary key. Primary keys are created only once and hence provide 
a constructor for primary key class and a get method in your bean class to 
access it. 
Mamata.

-----Original Message-----
From: "Amit Bhatia"<Amit.Bhatia@T...>
To: "Enterprise Java Beans"<enterprise_java_beans@p...>
Date: Mon Jun 11 04:59:58 PDT 2001
Subject: [enterprise_java_beans] Entity BEans in weblogic 6.0

>I am having the following problem in deploying entity Beans.
>	I want to use the get and the set methods only and hence i am having
>a declaration of them in the Remote.
>so all my abstract set and get methods are present in the Bean as well as in
>the remote.
>But my problem comes regarding the Primary Key. we are supposed to sheild
>the set method of the Primary key from the client and hence this method
>should not be present in the Remote.
>But since this is an abstract public method it should be present in both the
>remote and the bean.
>but this makes my primary key vunerable as the client can set it anytime.
>also if i dont include the setmethod in the remote but have it in the bean.
>then it gives an error while deploying saying that metrhods in remote not
>matching methods in bean.
>so what do i do?????
>Thanks in advance
>Amit