> a. it saves on creating unecessary entity beans and then calling the
> accessor/mutator methods on the many entity beans to get the data. A
> manually created select/insert statement increases efficiency
> in development
> time
Yes... if there is no data logic just exctract/insert (copying in other
words) its faster to use session beans. However if this is the only
thing your app do I would consider using something else besides EJB
> b. reduces network traffic therefore runtime speed.
Depends, if you are just copying no clients would be involved I guess.
However if the database resides on a different computer than the
appserver it would.
> c. reduces an uneceassry layer of tiers.
yes
===========================================================================
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".
