<snip>
> Suppose I have have the following:
>
> -Company
> - Division -> Employees
> - Dept
>
> What I would like to do is have a transient collection of Employees in
> Company, Division, and Dept so it's be easy to search only the relevant
> Employees. This seems pretty easy to setup and wouldn't be hard to
> implement. The one problem I can't seem to figure out is how do I keep
> the
> collections in sync. Modifying objects wouldn't be a problem but Adding
> and
> Deleting objects might. Do I have to use some sort of messaging to notify
> Company, Division, Dept Beans to update their internal collections? Is
> this
> where JMS would come in?
>
> Would this design be bad since all of the objects would have to be loaded?
>
>> the ejb's should be stateless in this regard. if the client
requests an employee collection, that collection is generated at call-time
and returned to the client - nothing remains on the ejb. when you want to
persist your altered collection, you call something like
Division.setEmployees(collection). this is simplistic but you get the idea.
===========================================================================
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".
