If you provide the setter methods in client view, assume the client trying to change the primary key means, for the updation purpose( i mean Bean to DB) the container couldn't find the primary for the bean, it resultant that a container would throw an exception.
So the conclusion is you can keep the setter methods in client view, it never disturb compilation and deployment process, but it would throw an exception while you calling in the client view.
So never disclosure your primary key fileds setter methods. It is not encouraged. Thats all.
Once the primary key for an entity bean has been set, the Bean Provider must not attempt to change it by use of set accessor methods on the primary key cmp-fields. The Bean Provider should therefore not expose the set accessor methods for the primary key cmp-fields in the component interface of the entity bean.
Although it won;t thown an exception if you expose the setter method but it is not a good practice.
Sawan<br />SCJP,SCWCD,SCBCD<br /> <br />Every exit is an entry somewhere.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: can setter methods exist for primary key?