Akeneo or Pim, Bundle or Component?¶
Since version 1.3, Akeneo PIM introduced components, that contain business logic or technical logic not coupled with Symfony Framework or Doctrine ORM / MongoDBODM, although Bundles contain the glue to assemble components together.
We use different namespaces, Akeneo for the technical parts not coupled with the PIM, Pim for the Community Edition parts and Enterprise suffix for the Enterprise Edition parts.
We organise the code as above in any new development and try to update legagy code as much as we can in each minor version to make the stack more and more understandable.
|(introduced v1.4) Data collector interfaces to aggregate statistics
|(introduced v1.5) Batch domain interfaces and classes (extracted from previous BatchBundle version)
|(introduced v1.5) Buffer domain interfaces and classes (extracted from previous BatchBundle version)
|(introduced v1.4) Generic classes for classification trees (implemented by product categories and asset categories) and tags
|(introduced v1.4) Utility classes to execute commands
|(introduced v1.4) Business interfaces and classes to handle files storage with filesystem abstraction
|(introduced v1.5) Localization domain interfaces and classes
|(introduced v1.3) Business interfaces and classes to abstract storage access (remover, saver, updater, repositories, etc)
|(introduced v1.5) Versioning domain interfaces and classes
|(introduced v1.4) PIM domain interfaces and classes, most of them still remain in CatalogBundle for legacy reasons
|(introduced v1.4) PIM business interfaces and classes to handle data import
|(introduced v1.4) Interfaces and classes related to collection of reference models and the product integration
Akeneo Enterprise components¶
|(introduced v1.4) File metadata readers
|(introduced v1.4) File transformer and native transformations
|(introduced v1.5) Generic action applier system
PIM Enterprise components¶
|(introduced v1.5) Rule engine implementation for product rules
|(introduced v1.4) Product asset domain and business classes
|(introduced v1.4) Workflow domain and business classes (most of them are still in WorkflowBundle)
Found a typo or a hole in the documentation and feel like contributing?
Join us on Github!