Good question... probably because it was originally implemented that
way and hasn't really been reviewed... ;)
In a way this should probably be an EECA because the grandTotal field
is really a derived/redundant field used for easy display, etc, and
not really an "original source" field, and EECAs are good for that. I
think at the time this was implemented the EECAs were not yet
implemented.
It could be a call within the service itself too. I'm not sure long
term which would be the better practice. In a way I think a set of
EECA rules would be easier to maintain over time as there are various
entities that have an effect on this field and the "rules" for
maintaining it could all site in one place. However, this also may
lead to more redundant calls to the grand total service as during the
whole storeOrder service it would be called a bunch of times.
-David
On Oct 13, 2006, at 12:54 AM, Si Chen wrote:
Hi.
Why is resetGrandTotal a SECA on createOrderAdjustment? Would
anybody have a problem if I just made it a service call inside
createOrderAdjustment?
Best Regards,
Si
[EMAIL PROTECTED]
