[osee-dev] Rationale for final methods in the Artifact class

["Brooks (US), Ryan D" <ryan.d.brooks@xxxxxxxxxx>]

OSEE Developers,

 

The integrity of the OSEE persistence layer, centered around artifacts, depends upon artifacts behaving as designed and expected by the rest of the framework.  This even includes some aspects of security.  If a subclass of artifact can override a relevant method it could subvert that.  Therefore, many of the methods of the Artifact class are declared final.  Additionally, we have been intentionally reducing the dependence upon subclassing from artifact.

 

Thanks,

Ryan