Vlada Matena wrote:
>One way to solve this is to use a "copy" object.
>(snip)
>Here you transfer the entire state of the entity object to the
>client.
>(snip)
>A variant on this is that instead of getting the copy of the
>*whole* object, you get only a copy of the part of the object
>that is used by the particular client use case.
Sending the entire state to the client as a "copy object" leads to designs
in which the business logic migrates to the client and the EJB server
becomes no more than an OODB - which is probably not what you chose EJB
for.
So use Vlada's variant, and design so that the business logic, including
input validation, stays on the server. If you need input validation on the
client for performance reasons repeat it there rather than move it from the
server to the client.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
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".
