Andrew Stevens escreveu:
> Easy enough to do, just have the DAO calls in the subclass
> check for non-abstract super before calling the DAO (in fact, what the
> hell, it might as well do this on *all* dao.call methods). Plus, if we
> rely on people setting the fields' values in the super ejbC
Okay, I'm going round in circles thinking about the best way to handle this,
so I figure its time to get some more opinions...
I'm looking at bug #545622; basically the problem is that the create methods
I generate in the DAO don't include a reference to the bean, so you can't
update values in
>
> Any opinions on the best way to handle EJB lifecycle events
> through DAOs?
> I've got two main choices, and I'm not sure which way to jump:
>
> a) use DataObjects to pass around the state values between
> the bean and the
> DAO
Mmm DO are only there for external world imho
> or
> b)
Any opinions on the best way to handle EJB lifecycle events through DAOs?
I've got two main choices, and I'm not sure which way to jump:
a) use DataObjects to pass around the state values between the bean and the
DAO
or
b) pass a reference to the bean to the DAO.
e.g. ejbLoad would either cal
