Hey
punit malik wrote:
> 1. Primary key: both entity and session have primary key. It is different
> that programmer shouldn't call it in session as it is for container.
Sessions do not have a primary key. Specifically stateless session beans
do not have any identity whatsoever. And since the stateful session bean
identity is for internal use only, as you note, from a bean or client
programmer perspective this is the same as not having a primary key.
> I don't see anything else which is reflected in EJBObject that is
> conflicting for the two.
That is true. Whether or not to use two interfaces is essentially a
design issue. It can be argued that by introducing 2 separate interfaces
(Entity, Session) with a common superinterface EJBObject the
specification becomes more complex than is necessary since there is so
little difference. Specifically Session would be empty(!). Because of
this I agree with the current design.
Simplicity simplicity simplicity...
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
