Yes, this is the technique. Usually this method is implemented in a session
bean. This gives you an easier way to break it down into customizable
views...
jim
> -----Original Message-----
> From: JB Steadman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 19, 1999 5:51 PM
> To: [EMAIL PROTECTED]; James Cook
> Subject: Re: Inheritance and EJB
>
>
> Do you think it's necessary that your data encapsulation object
> be an instance variable of your bean? One could imagine the
> following methods on an entity bean:
>
>
> public BeanData getBeanData() {
> BeanData data;
>
> data = new BeanData();
> data.var1 = this.var1;
> data.var2 = this.var2;
> ...
> ...
>
> return data;
> }
>
> public void setBeanData(BeanData newData) {
>
> this.var1 = newData.var1;
> this.var2 = newData.var2
> ...
> ...
> }
>
> This permits CMP. The downside, obviously, is that a new object
> is created with each call to getBeanData().
>
===========================================================================
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".
