Spring into action with Commerce Beans

I have been writing a lot about CoreMedia, the Studio, and of course the many cool features you have for your eCommerce integration; but one piece I have yet to mention is the underlying technology and architecture – which in many regards is even more impressive.

The good news is, if your company has expertise with Spring or Spring Boot then you are in luck! Our Content Application Engine (CAE) provides tools and a framework with which you can easily design a beautiful, consistent, and fully-functional user experience. The CAE is based on the Spring MVC framework, so if you are familiar with data beans and content beans it should be very easy for you. This also means you can use Freemarker templating for your preview and end channel renderings. If you are not familiar with Freemarker then you might want to check out this blog and learn why you should move your JSP templates to Freemarker: 10 Reasons to Replace Your JSPs With FreeMarker Templates.

In Spring, the objects that form the backbone of your application and that are managed by the Spring IoC container are called beans. A bean is an object that is instantiated, assembled, and otherwise managed by a Spring IoC container. – link

Basing the core platform on Spring should be comforting considering the many custom platforms out there where you need specialized skills, custom frameworks, or antiquated technologies like PHP. Using an industry standard and widely used framework like Spring insures your ability to find the right technical resources.

The following are the beans we have for our eCommerce integrations in CoreMedia:

Screen Shot 2019-03-05 at 3.07.08 PM.png

Defines a catalog item as common interface of all commerce beans.

Defines an interface for a shopping cart representation.

Defines an interface for a shop category.

Defines an interface for a product variant.
With the extension of the product interface it should behave as the base product itself in many ways.

Defines a interface for a store user.

Defines an interface for a catalog representation.

Contract represents commerce-side user contracts.

Defines an interface for a product representation.

Segment represents commerce-side user segments.

These beans are what make the integration with the various eCommerce platforms so seamless, which, in the end allows me to create such simple videos like this play list:

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.