meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
sap_hybris_commerce:orders:commerce_facades_key_concepts_features [2019/08/26 16:51] – [Key Features] Antonio Robirosasap_hybris_commerce:orders:commerce_facades_key_concepts_features [2019/12/18 20:17] (current) – external edit 127.0.0.1
Line 2: Line 2:
 The **commercefacades** extension exposes a group of facades which simplify the communication between the store frontend and the service layer. This is a summary which I wrote while studying for the certification. The Hybris Documentation about commercefacades has one page and it is worth reading. The **commercefacades** extension exposes a group of facades which simplify the communication between the store frontend and the service layer. This is a summary which I wrote while studying for the certification. The Hybris Documentation about commercefacades has one page and it is worth reading.
  
-====== Key Concepts ======+===== Key Concepts ======
  
   * The facades return **data objects** which are completely separated from the models. They can be extend using the file ***-beans.xml.**   * The facades return **data objects** which are completely separated from the models. They can be extend using the file ***-beans.xml.**
Line 17: Line 17:
       * Then a configurable populator fills the fields which are only required by some components/pages of the front-end. It has a Map<Enum option, populator>.       * Then a configurable populator fills the fields which are only required by some components/pages of the front-end. It has a Map<Enum option, populator>.
     * [[https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/6.5.0.0/en-US/8b937ff886691014815fcd31ff1de47a.html|A class diagram can be found here]]     * [[https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/6.5.0.0/en-US/8b937ff886691014815fcd31ff1de47a.html|A class diagram can be found here]]
-====== Key Features ======+===== Key Features ======
  
   * There are facades for:   * There are facades for:
Line 38: Line 38:
   * The **URLResolver** must be implemented to provide relative URLs for the business objects. Hybris comes with URL resolvers for products, categories and search using facets.   * The **URLResolver** must be implemented to provide relative URLs for the business objects. Hybris comes with URL resolvers for products, categories and search using facets.
  
-====== Workflow ======+===== Workflow ======
  
-The interaction of the controllers, facades, services, DAOs, models and data objects is explained in the this diagram: +The interaction of the controllers, facades, services, DAOs, models and data objects is explained in the this diagram: [[https://wiki.hybris.com/download/attachments/289441083/Simple%20Request%20Interaction%20Diagram.jpg?version=1&amp;modificationDate=1444256224000&amp;api=v|Simple Request Interaction Diagram.jpg]]
- +
-{{https://wiki.hybris.com/download/attachments/289441083/Simple%20Request%20Interaction%20Diagram.jpg?version=1&amp;modificationDate=1444256224000&amp;api=v2&.jpg?|Simple Request Interaction Diagram.jpg}}+
  
 **In the B2C Accelerator the converters and the populators are never used to convert from a DTO to a model.** But they could be used. **In the B2C Accelerator the converters and the populators are never used to convert from a DTO to a model.** But they could be used.
  
 --Based on Hybris 6.3 --Based on Hybris 6.3