Frequently Asked Questions

Bellow are answers to the most common questions about Salmon!

E2C server-side is written in Java while the client-side is in JavaScript. We tested and ran E2C server-side in Glassfish V3 with MySQL and recommend this environment.
As with any Java web application, you need a container (i.e. Glassfish, Tomcat). A database is strongly recommended for data serialization. At this time E2C binaries are only available for Windows Server. Memory, and hard drive space vary depending upon your use, as E2C is very scalable. For instance, if you wish to use memory caches, you will need to allocate sufficient memory.
The client-side is fully editable using JavaScript, which, in most cases, allows you to extend E2C simply because it relies on the server generic API, which you will see covers the vast majority of possibilities. This is plenty to modify or add many features as it handles communication with the server and removes many of the complications for you.

Server-side source code is not disclosed, but should you have an advanced need (well beyond general use), you can override classes in Java to modify their behavior. Furthermore, you can add your very own servlets, beans, and filters to E2C server.

You may also run other languages, like JavaScript, PHP, etc., inside Glassfish, the container that EC2 uses.
Absolutely. JavaScript lets you add or modify features though E2C client-side code. For most web sites, you either access or transmit data and apply some logic (i.e. cart, checkout, calculations). Most of this logic is already synthesized, so you only need to call on the server relevant API function from client-side JavaScript.
Yes. This is an important feature, allowing you to virtually extend E2C to handle any industry specific task that it was not originally designed to do. E2C's flexible data model processing makes this possible.
Not at all. You may build your web pages as you would do for any regular/static web site. Feel free to use any standard HTML mock-up. Then simply add E2C JavaScript calls to the pages. A template may make things easier, but is not required.
Absolutely! Use any design you like, including ones designed for other systems. Some systems have complicated templating systems, which mix web design and application code using a specific folder structure, thus splitting the HTML code into various parts. In that case, you may need to reconsolidate it into an HTML template.
An HTML template is a web design template that is not specific to any particular solution or system. For comparison, a Joomla template, a Flash template, or a Magento template, are templates specifically designed for those particular systems.
Starting from an HTML template or an HTML mock-up, you add DOM element IDs, like this:

<span id="e2cproduct_name8">

where you want the data to render. A simple E2C client-side JavaScript function call, like this:


for example, on page load, will then populate the page with the relevant data dynamically.