On Mon, 07 Feb 2000, Laird Nelson wrote:
>
> On the other hand, if you call a single method on a
> session bean, then one method invocation request goes across the wire
> from the client to the bean, which then typically can converse with the
> entity bean in the same container.
yeah, I think we all have the same idea, more or less, of what makes sense. Few
circumstances would argue for a client to directly access an entity bean.
And, as others have said, it makes sense to put behavior directly in an entity
bean as long as that behavior is broadly applicable. More application-specific
behavior problably belongs in a session bean.
And if you think about it, all of these guidelines just make good programming
sense. In the normal Java world, we wouldn't make any one object too complex.
We might have helper classes that provide additional functionality.
> Finally, though, when the so-called "business logic" (I hate that term
> with a passion; what if I'm designing a system that doesn't have
> anything to do with "business"? :-))
I've considered this 'semantic' problem, and I think you just have to think of
the word "business" the way you did when you were a little kid, as in "it's
none of your business". That is, "business" is the way we conduct our affairs.
The military doesn't conduct business (usually :-) but they're in the business
of making large hills into small ones. That's their business, and they
certainly have lots of business rules on how to do that. :^)
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
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".
