your problem seems to be 100% presentation. Business logic shouldn't
know anything about confirmation pages, because it's not a part of the
business use case.
Business logic should provide you the methods to perform the checks.
like:
in First Update Action:
if (service.hasKeyPairMoved())
se
Um, what is a keypair? A primary key?
I personally prefer to have "store" actions and "view" actions. In my
"store" action I would call some business code which verifies that
object can be saved automatically. And if not, then if "overwrite"
flag is set by client. If yes, store and show "view".
I
Hi again,
My apologies for a probably obvious problem. I've got an example
where I need to check (on update) if this object is actually being
'moved' (ie, keypair is being changed), and if there is already data at
the dest. keypair, go back to the page, display both objects and confirm
the us
3 matches
Mail list logo
