Following is a list of the common ways to customize SoftSlate Commerce, and suggestions for how to proceed with incorporating each type of customization from 1.x to 2.x.
Custom Java Classes.
A number of interface changes were made in the API from 1.x to 2.x. You will need to be aware of these changes, and may need to update your custom Java classes to conform to the new API. For a list of these interface changes, visit the following section of the Migration Guide.
Another important change from 1.x to 2.x is that the custom implementations of the
various interfaces are no longer stored as settings in the
npcSetting database table. They are now stored in the
/WEB-INF/classes/appComponents.properties file. When
you are ready to test your custom classes, you must either update this file manually,
or you may use the
Store Settings ->
Components screen to modify the file through the 2.x
To identify a custom implementation of a Java class in 2.x, you must either
Custom SQL Queries.
If you created custom SQL queries for 1.x in one of more of the
sql-custom.properties files found under the
subdirectories of the
directory, you may create analogous queries in the
queries-custom.hbm.xml files in the same directories in
Please be aware, however, that the
queries-custom.hbm.xml files are used by Hibernate, and
consist of queries written in the
Hibernate Query Language (HQL). A working knowledge of Hibernate and HQL is
essential to writing custom queries.
Because SoftSlate Commerce 2.x employs Hibernate, custom queries are written in the Hibernate Query Language (HQL), rather than SQL.
Custom JSP Templates.
In a few cases, the default JSP templates have changed dramatically. Pay special
note to the list of JSP template
changes in the following section of the Migration Guide. If you created
custom JSP template in the
directory, they may need to be updated to interact correctly with the default 2.x
templates. A good way to go about incorporating the customizations is to copy each
custom JSP template over to the 2.x installation one at time, and testing each one for
errors or other issues.
Custom Struts Configurations.
Any custom Struts configurations you made in
translate directly to 2.x. Simply copy the file over to 2.x, and test the custom form
beans and actions to make sure there are no complications.
Because of the interface changes from 1.x to 2.x, your custom Struts action classes may need to be modified to conform to the new API.
Custom Tiles Definitions.
Custom Tiles definitions you made in
/WEB-INF/conf/core/tiles-defs-custom.xml . should
translate directly from 1.x to 2.x. Be sure to test them after copying the file from the
1.x to 2.x installation.
Numerous interface changes were made to simplify the API and adapt it for use with the Hibernate persistance framework. Keep the following changes in mind as you incorporate any Java class customizations from 1.x into 2.x.
In a few cases, the default JSP templates have changed dramatically. Because of this, we recommend installing 2.x from scratch and incorporating any custom JSP templates you created into the corresponding 2.x templates manually. As you do so, keep the following major JSP template changes in mind: