Hi,
> Do you not define the fine grain accessors on the entity bean since they
> are on the value object? Meaning a remote client should be calling the
> getDetails() method, but what about a session bean which might be in the
> same JVM. Does it also need to fetch the details object and then get the
> attribute out of it, or can it call a fine grain accessor on the entity
> bean?
One could use a private value object to hold the attribute values (instead of
several 'direct' member attributes), and still provide fine-grained access
methods, like
public int getAtt1() {
return value.att1;
}
The advantage would lie in the avoidance of code redundancy
cu
Heiko
===========================================================================
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".
