[EMAIL PROTECTED] wrote:
I don't understand Dave's concern. Perhaps he would elaborate on why he says to
avoid Session beans.
Anything EJB-related I've run in to (except in a few instances) has been
mind-blowing overkill, that's all.
I'm not saying they're _never_ the right answer, and I might change my
mind with the latest EJB spec (at least a little), but the footprint
required for their use seems biggish for the benefits derived. In most
cases ;)
However, it may be that he would favor POJOs if the container isn't really giving your app anything (why go through the trouble of EJB in other words).
I would ;)
Another camp would tell you to just use something like a business delegate + iBatis or Hibernate. I cannot comment as I have not used that approach.
This is the approach I've used the most and it seems to work pretty well
for me--it's very simple and keeps Actions clean and relatively
maintenance-free.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
