THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Hybris Features | Hybris Feature Capabilities | Ofbiz Standing | Gap | Comment |
|---|---|---|---|---|
| Spring Framework | The hybris Commerce Accelerator makes heavy use of the Spring Framework to manage dependencies between components. We have a clear separation between a component's interface and its implementation. To replace an implementation with your own you just need to register your own implementation in a Spring XML configuration file. Doing so you can easily extend or modify existing behaviour | ?? |
| Spring Integration | The hybris Commerce Accelerator may interface with many external systems. For example, warehouses for fulfillment, CRM systems for customer data, and product and order databases. To communicate with these systems, hybris supports the required data transport protocol and converts information to and from the required data format. This data communication is carried out in a well-defined way using Enterprise Integration Patterns (EIPs). Rather than using a bespoke solution, hybris implements EIPs with Spring Integration - a comprehensive, non-invasive framework that is adaptable for a wide variety of data transfer protocols and is based on a message-driven architecture that makes it easier to decouple components | ?? |
|---|
| Spring Security | hybris relies on standards such as Spring Security to protect organizations’ IT environments and data. Spring security provides advanced authentication, authorization and other security features to define user identity and limit access to secured resources | ?? |
|---|
| Spring MVC 3 | Spring MVC 3 (Model View Controller) is the Web component of Spring’s framework. It provides rich functionality and guidelines for building robust online stores. The Spring MVC framework is designed so that every piece of logic and functionality is highly configurable. The separation of logic and data view simplify maintenance | ?? |
|---|
| Façade Layer | The façade layer provides a simplified interface to the hybris Service Layer. A façade orchestrates service to reduce the complexity among subsystems. Communication is simplified because the code is easy to read, understand, and test. Also, façades can be easily mocked and therefore can help separate frontend from backend development | ?? |
|---|
JSP based View Layer | The storefront uses JSP 2.1 as its view rendering technology. Basically, the View Layer is the conduit for getting data in and out of the application. It is the layer that concentrates on the interface and manages business logic and data access. The use of standard technologies such as JSP in the view layer simplifies the adoption of the Commerce Accelerator storefront. There are several different groups of JSPs - page, fragements and CMS JSPs. | ?? |
|---|
| Page JSP contains JSPs that are used to render a complete HTML web page that can be returned to the client browser. | ?? |
| Fragments JSP contains JSPs that are used to render parts of HTML web pages that are requested or updated asynchronously. This is used to handle functionality like the product quick view pop-up. The product quick view pop-up is requested by the client browser via an Ajax request. The view is rendered for a specific product and returned to the client browser. The client browser then inserts this HTML into the web page | ?? |
| CMS JSP contains JSPs that are used to render the view for specific CMS components such as cart, checkout, promotion, my account and many more | ?? |
| AJAX | hybris uses the jQuery, a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid Web development. jQuery is designed to enable developers to more easily and quickly write JavaScript. The richness and responsiveness of AJAX improves the customer experience in online stores. Instead of loading a webpage at the start of a session, the browser loads an Ajax engine written in JavaScript. Processing occurs instantly, with no waiting for pages to reload---e.g., when a shopping cart is updated |
|---|
| yes | Though not extensively implemented |
| Data model | Each Storefront will have a counterpart CMS Site and Base Store. These are the central objects for configuring a new website. While setting up the CMS Site, you will link the Site to the appropriate Catalogs that hold the content for the Storefront. Catalogs are used to store Product and WCMS content. The Content Catalog stores all the WCMS pages, components and templates. The Product Catalog stores all product and category data | ?? |
|---|
| Sample store | Functionally rich Sample Stores demonstrate available Commerce Accelerator functionality including Landing Pages, Product Pages, Faceted Search and Navigation, Shopping Cart, Full Checkout Process, My Account, Order History, Content Pages and the B2B My Organization area |
|---|
| Yes | via project demos | |
| Sample data | hybris provides extensive sample data which enables customers and partners to test the usage of the existing functionality on the real data. Sample data include all complete examples of using ImpEx, CMS Content, two product catalogs with classification, product references, categorization, media, prices, promotions, BTG segments and rules, store locator, points of sale and example B2B organization structures |
|---|
| yes | extensive demo data available | |
| jQuery Mobile | hybris uses the jQuery mobile UI toolkit for building the cross platform mobile storefront |
|---|
| WURFL Library | hybris uses the WURFL library (http://wurfl.sourceforge.net/) to segment devices which also allows for additional separate UI experiences to meet future requirements. An example is a separate experience for tablet users | ?? |
|---|