Common Apex Library supporting Apex Enterprise Patterns and much more!
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
Dependencies: Must deploy ApexMocks before deploying this library
git log --followfrom the command line or refer to this tag of the codebase prior to conversion.
fflib_SObjectDomain.onValidate(Map existingRecords)methods where called during an on after update trigger event. From this point on the
onValidate()method will only be called during on after insert. If you still require the orignal behaviour add the line
Configuration.enableOldOnUpdateValidateBehaviour();into your constructor.
Is derived from the Dreamforce 2012 presentation on Apex Enterprise Patterns and progresses the patterns further with a more general ongoing home for them. It also adds some form of namespace qualification from the previous version. So that classes are grouped together more easily in the IDE's and packages. Below you can find comprehensive articles and videos on the use of these patterns. There is also a working sample application illustrating the patterns here.
Design patterns are an invaluable tool for developers and architects looking to build enterprise solutions. Here are presented some tried and tested enterprise application engineering patterns that have been used in other platforms and languages. We will discuss and illustrate how patterns such as Data Mapper, Service Layer, Unit of Work and of course Model View Controller can be applied to Force.com. Applying these patterns can help manage governed resources (such as DML) better, encourage better separation-of-concerns in your logic and enforce Force.com coding best practices.
Other Related Blogs