@PublicSpi can expect
that programs compiled against a given version will remain binary compatible with later versions of the
@PublicSpi as per each product's API policy (clients should refer to each product's API policy for
the exact guarantee -- usually binary compatibility is guaranteed at least across minor versions).
@PublicSpiinterfaces and classes are specifically designed to be implemented/extended by clients. Hence, the guarantee of binary compatibility is different to that of
@PublicApielements (if an element is both
@PublicSpi, both guarantees apply).
This interface is used as a callback mechanism in the case where "runnable code" has completed
postCall determines that it did not clean
up properly. Typically, all that can be done is to log the problem, but this interface
allows the detection of the problem and its logging to be separated, as the caller may be
able to provide more helpful information.
Called when the
postCall determines that the runnable
code began a org.ofbiz.core.entity.TransactionUtil database transaction and failed to
rollback the transaction
before it finished. This could result in data inconsistencies, so the runnable code
should be fixed to handle transactions properly.