本文共 1212 字，大约阅读时间需要 4 分钟。

--Motivation

hybris' Cuppy Extension has been written specifically to demonstrate hybris' best practices and coding conventions. It provides a valuable resource for developers learning how to adapt the hybris Suite. In contrast to most of hybris' extensions, Cuppy does not address ecommerce use-cases, rather it provides an environment for users to place bets on upcoming football matches. Focusing on non-ecommerce related use-cases, we hope to ensure that trainees fully understand concepts of a certain topic before applying them to their own domain.

--Access the Cuppy Site

Go to and login with username pp and password1234

--Basic Roadmap

We know from our basic understanding of the that:

• Web clients should communicate with hybris via a façade, using Data Transfer Objects (DTOs) to transfer data
• The façade can communicate with services in the ServiceLayer to obtain data and perform business logic
• Services in the ServiceLayer transfer the Data Entities using hybris Models
• We should separate DAO logic into separate DAOs
• All our classes should be tested (unit tests are suitable for testing classes in isolation whereas integration tests are suitable for testing classes within a hybris "live" context)

转载地址：https://blog.csdn.net/xxxcyzyy/article/details/49051235 如侵犯您的版权，请留言回复原文章的地址，我们会给您删除此文章，给您带来不便请您谅解！