The goal when designing distributed systems is to minimize network traffic. (At least that is my goal...) One common solution to this is to have a single method to get all attributes (or a number of attributes) from an EB and one single metod to set all attributes in an EB, e.g. public void setAllAttributes(...) public ... getAllAttributes() I have used three structures to implement this (I'm sure there are many more.): 1. For every EB implement a data holder object. For the EB Customer you make a CustomerData that contains all the primitive attributes (int, String, ...) that the EB Customer has. Now you can use CustomerData as argument in setAllAttributes and as return type in getAllAttributes. CustomerData can easily be generated from the EB Customer. You can also put simple validation code in CustomerData. 2. Pass a hashtable between the client and the server. Use the name of the attributes as keys. 3. Name-Value pairs. Much the same as a hashtable. Hope this helps /Tommy >Hi, > >I have a need to make certain methods within an EntityBean available to the >client application (such as set() and get() methods on cached data, >validate() on cached data) without invoking a remote network call. In order >to do this would I have to send the actual Entity Bean instance to the >client? This seems like a horrible solution to me - are there any >suggestions? I hope I am missing something. > >Thanks in advance, Lisa > >=========================================================================== >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". > > =========================================================================== 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".
