2.2 to 3.0 Migration

    <target name="build-create-sql">
        <!--
            You will need to run a mvn install on your project before attempting to execute this task.
            Also, you will likely need to assign additional heap space to your ANT process. A setting
            of -XX:MaxPermSize=256M -Xmx512M should be sufficient.

            This can be done by populating the 'ANT_OPTS' environment variable:
                export ANT_OPTS=-XX:MaxPermSize=256M -Xmx512M
            which will ensure those settings for all ant processes. Alternatively you could use JAVA_OPTS which is for
            the global JVM and will effect all Java processes.
        -->
        <mkdir dir="target/sql/create"/>
        <artifact:pom id="myPom" file="pom.xml" />
        <artifact:dependencies filesetId="pomDeps" pomRefId="myPom" useScope="compile" />
        <property name="baseTarget" location="target/${myPom.build.finalName}/WEB-INF"/>
        <fileset id="libDir" dir="${baseTarget}/lib"/>
        <path id="build.runtime.classpath">
            <!--There are some additional libraries needed at compile time that are not included
                in WEB-INF/lib - find those libraries via a difference algorithm-->
            <restrict>
                <difference>
                    <fileset refid="pomDeps" />
                    <intersect>
                        <fileset refid="pomDeps" />
                        <fileset refid="libDir" />
                    </intersect>
                </difference>
                <rsel:not>
                    <rsel:name name="**/*.pom" />
                </rsel:not>
            </restrict>
            <!--Add the lib directory to get all the dependencies required for the demo app-->
            <fileset refid="libDir"/>
            <dirset dir="src/main/resources" />
            <!--Add the classes directory in the war project, if required-->
            <!--<pathelement location="${baseTarget}/classes"/>-->
        </path>
        <!--If the war project does not contain custom entities (best practice), then it is not necessary to include application context from the WEB-INF directory-->
        <!--<property name="my.app.context" location="src/main/webapp/WEB-INF/applicationContext.xml"/>-->
        <taskdef name="hibernatetool" classname="org.broadleafcommerce.common.util.sql.HibernateToolTask" classpathref="build.runtime.classpath"/>
        <hibernatetool destDir="target/sql/create" combinePersistenceUnits="false" refineFileNames="true">
            <!--add in additional persistence configuration related to the cms -->
            <classPathApplicationContext path="bl-cms-contentClient-applicationContext.xml"/>
            <classPathApplicationContext path="bl-open-admin-contentClient-applicationContext.xml"/>
            <!--add in additional persistence configuration for our core -->
            <classPathApplicationContext path="applicationContext.xml"/>
            <!--see description for my.app.context above -->
            <fileSystemApplicationContext path="src/main/webapp/WEB-INF/applicationContext.xml"/>
            <classPathApplicationContext path="bl-fake-applicationContext-ant.xml"/>
            <!--select the dialects and persistence units to export-->
            <jpaconfiguration persistenceUnit="blPU" dialect="${ant.hibernate.sql.ddl.dialect}" />
            <jpaconfiguration persistenceUnit="blSecurePU" dialect="${ant.hibernate.sql.ddl.dialect}" />
            <jpaconfiguration persistenceUnit="blCMSStorage" dialect="${ant.hibernate.sql.ddl.dialect}" />
            <!--other required elements-->
            <classpath refid="build.runtime.classpath" />
            <hbm2ddl export="false" update="false" create="true"/>
        </hibernatetool>
    </target>

    <target name="build-update-sql">
        <!--
            You will need to run a mvn install on your project before attempting to execute this task.
            Also, you will likely need to assign additional heap space to your ANT process. A setting
            of -XX:MaxPermSize=256M -Xmx512M should be sufficient.

            This can be done by populating the 'ANT_OPTS' environment variable:
                export ANT_OPTS=-XX:MaxPermSize=256M -Xmx512M
            which will ensure those settings for all ant processes. Alternatively you could use JAVA_OPTS which is for
            the global JVM and will effect all Java processes.
        -->
        <mkdir dir="target/sql/update"/>
        <artifact:pom id="myPom" file="pom.xml" />
        <artifact:dependencies filesetId="pomDeps" pomRefId="myPom" useScope="compile" />
        <property name="baseTarget" location="target/${myPom.build.finalName}/WEB-INF"/>
        <fileset id="libDir" dir="${baseTarget}/lib"/>
        <path id="build.runtime.classpath">
            <!--There are some additional libraries needed at compile time that are not included
                in WEB-INF/lib - find those libraries via a difference algorithm-->
            <restrict>
                <difference>
                    <fileset refid="pomDeps" />
                    <intersect>
                        <fileset refid="pomDeps" />
                        <fileset refid="libDir" />
                    </intersect>
                </difference>
                <rsel:not>
                    <rsel:name name="**/*.pom" />
                </rsel:not>
            </restrict>
            <!--Add the lib directory to get all the dependencies required for the demo app-->
            <fileset refid="libDir"/>
            <dirset dir="src/main/resources" />
            <!--Add the classes directory in the war project, if required-->
            <!--<pathelement location="${baseTarget}/classes"/>-->
        </path>
        <!--If the war project does not contain custom entities (best practice), then it is not necessary to include application context from the WEB-INF directory-->
        <!--<property name="my.app.context" location="src/main/webapp/WEB-INF/applicationContext.xml"/>-->
        <taskdef name="hibernatetool" classname="org.broadleafcommerce.common.util.sql.HibernateToolTask" classpathref="build.runtime.classpath" />
        <hibernatetool destDir="target/sql/update" combinePersistenceUnits="false" refineFileNames="true">
            <!--add in additional persistence configuration related to the cms -->
            <classPathApplicationContext path="bl-cms-contentClient-applicationContext.xml"/>
            <classPathApplicationContext path="bl-open-admin-contentClient-applicationContext.xml"/>
            <!--add in additional persistence configuration for our core -->
            <classPathApplicationContext path="applicationContext.xml"/>
            <!--see description for my.app.context above -->
            <fileSystemApplicationContext path="src/main/webapp/WEB-INF/applicationContext.xml"/>
            <classPathApplicationContext path="bl-fake-applicationContext-ant.xml"/>
            <!--select the dialects and persistence units to export-->
            <jpaconfiguration persistenceUnit="blPU" dialect="${ant.hibernate.sql.ddl.dialect}" 
                url="${ant.blPU.url}" 
                userName="${ant.blPU.userName}" 
                password="${ant.blPU.password}" 
                driverClassName="${ant.blPU.driverClassName}"/>
            <jpaconfiguration persistenceUnit="blSecurePU" dialect="${ant.hibernate.sql.ddl.dialect}" 
                url="${ant.blSecurePU.url}" 
                userName="${ant.blSecurePU.userName}" 
                password="${ant.blSecurePU.password}" 
                driverClassName="${ant.blSecurePU.driverClassName}"/>
            <jpaconfiguration persistenceUnit="blCMSStorage" dialect="${ant.hibernate.sql.ddl.dialect}" 
                url="${ant.blCMSStorage.url}" 
                userName="${ant.blCMSStorage.userName}" 
                password="${ant.blCMSStorage.password}" 
                driverClassName="${ant.blCMSStorage.driverClassName}"/>
            <!--other required elements-->
            <classpath refid="build.runtime.classpath" />
            <hbm2ddl export="false" update="true" create="false"/>
        </hibernatetool>
    </target>
    ```

-------------

**Item**: Update your current 2.2 database schema to be 3.0 compliant

1. Via ANT, execute the "build-update-sql" task in site/build.xml (will take a few minutes to run)
    - This task should launch a lightweight version of Broadleaf's domain and your domain extensions
    - A comparison is performed against this combined domain and the target schema
    - The result of this comparison is an update sql file that can be run against your existing schema to alter its structure to be 3.0 compliant
    - Open the emitted update sql file: site/target/sql/update/\*Dialect\_blPU.sql
    - Execute the contents of this sql file against your target schema using your favorite sql execution environment

-------------

**Item**: Update admin permissions

1. The most straightforward approach is to remove old information and repopulate
    - If you've done a lot of role customization for admin users, then this section will require some diligence, as you will need to manually rebuild your associations between roles and permissions. You may want to record the permissions you have associated with each role (see your `BLC_ADMIN_ROLE_PERMISSION_XREF` table) so that you can recreate these with the repopulated information.
    - Refer to the following table of standard roles and required permissions in 3.0. This can be used as a guide.

    | Role Name                    | Permission Name                      |
    | -------------------------    | ----------------------------------   |
    | ROLE\_CONTENT\_APPROVER      | PERMISSION\_ALL\_APPROVER\_SANDBOX   |
    | ROLE\_CONTENT\_APPROVER      | PERMISSION\_ALL\_STRUCTURED\_CONTENT |
    | ROLE\_CONTENT\_APPROVER      | PERMISSION\_ALL\_ASSET               |
    | ROLE\_CONTENT\_APPROVER      | PERMISSION\_ALL\_PAGE                |
    | ROLE\_CONTENT\_APPROVER      | PERMISSION\_OTHER\_DEFAULT           |
    | ROLE\_CONTENT\_EDITOR        | PERMISSION\_ALL\_USER\_SANDBOX       |
    | ROLE\_CONTENT\_EDITOR        | PERMISSION\_ALL\_STRUCTURED\_CONTENT |
    | ROLE\_CONTENT\_EDITOR        | PERMISSION\_ALL\_ASSET               |
    | ROLE\_CONTENT\_EDITOR        | PERMISSION\_ALL\_PAGE                |
    | ROLE\_CONTENT\_EDITOR        | PERMISSION\_OTHER\_DEFAULT           |
    | ROLE\_CUSTOMER\_SERVICE\_REP | PERMISSION\_ALL\_CUSTOMER            |
    | ROLE\_CUSTOMER\_SERVICE\_REP | PERMISSION\_ALL\_ORDER\_ITEM         |
    | ROLE\_CUSTOMER\_SERVICE\_REP | PERMISSION\_ALL\_FULFILLMENT\_GROUP  |
    | ROLE\_CUSTOMER\_SERVICE\_REP | PERMISSION\_ALL\_ORDER               |
    | ROLE\_CUSTOMER\_SERVICE\_REP | PERMISSION\_OTHER\_DEFAULT           |
    | ROLE\_PROMOTION\_MANAGER     | PERMISSION\_ALL\_PROMOTION           |
    | ROLE\_PROMOTION\_MANAGER     | PERMISSION\_OTHER\_DEFAULT           |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_CURRENCY            |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_SEARCHFACET         |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_ASSET               |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_SKU                 |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_PRODUCT\_OPTION     |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_PRODUCT             |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_ALL\_CATEGORY            |
    | ROLE\_MERCHANDISE\_MANAGER   | PERMISSION\_OTHER\_DEFAULT           |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_MODULECONFIGURATION |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_CURRENCY            |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_SEARCHFACET         |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_SEARCHREDIRECT      |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_URLHANDLER          |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_ADMIN\_USER         |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_APPROVER\_SANDBOX   |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_USER\_SANDBOX       |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_STRUCTURED\_CONTENT |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_ASSET               |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_PAGE                |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_CUSTOMER            |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_ORDER\_ITEM         |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_FULFILLMENT\_GROUP  |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_ORDER               |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_PROMOTION           |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_SKU                 |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_PRODUCT\_OPTION     |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_PRODUCT             |
    | ROLE\_ADMIN                  | PERMISSION\_ALL\_CATEGORY            |
    | ROLE\_ADMIN                  | PERMISSION\_OTHER\_DEFAULT           |

2. Clear out the `BLC_ADMIN_ROLE_PERMISSION_XREF` table to avoid constraint violations during the next steps

3. Clear out the `BLC_ADMIN_PERMISSION_ENTITY` table so that new values can be imported

4. Clear out the `BLC_ADMIN_PERMISSION` table so that new values can be imported

5. Download the re-population sql: <https://github.com/BroadleafCommerce/BroadleafCommerce/blob/broadleaf-3.0.0-GA/core/broadleaf-framework/src/main/resources/config/bc/sql/load_admin_permissions.sql>

6. Execute the re-population sql against your database using your favorite sql execution environment

7. Rebuild your `BLC_ADMIN_ROLE_PERMISSION_XREF` table mapping your custom roles to the appropriate permissions
    - If you have **NOT** altered any roles and took advantage of the roles from the 2.2 demo starter project, you can execute the following in your favorite sql execution environment to rebuild the `BLC_ADMIN_ROLE_PERMISSION_XREF` table.

    ```sql
    -- Super User
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-6);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-11);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-16);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-21);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-26);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-31);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-36);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-41);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-46);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-51);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-56);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-61);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-62);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-63);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-68);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-73);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-78);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-83);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-88);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (1,-93);

    -- Merchandiser
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-6);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-11);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-16);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-21);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-56);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-83);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (2,-88);

    -- Promotions
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (3,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (3,-26);

    -- CSR
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (4,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (4,-31);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (4,-36);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (4,-41);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (4,-46);

    -- CMS Editor
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (5,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (5,-51);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (5,-56);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (5,-61);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (5,-62);

    -- CMS Approver
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (6,-1);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (6,-51);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (6,-56);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (6,-61);
    INSERT INTO BLC_ADMIN_ROLE_PERMISSION_XREF (ADMIN_ROLE_ID, ADMIN_PERMISSION_ID) VALUES (6,-63);
    ```

-------------

**Item**: Add data for admin sections and modules

1. Download the population sql: <https://github.com/BroadleafCommerce/BroadleafCommerce/blob/broadleaf-3.0.0-GA/core/broadleaf-framework/src/main/resources/config/bc/sql/load_admin_menu.sql>

2. Delete your current `BLC_ADMIN_MODULE` and `BLC_ADMIN_SECTION` tables

3. Execute the population sql against your database using your favorite sql execution environment

-------------

**Item**: Address Hibernate 4 change for boolean fields from Bit to TinyInt (applies to MySql)

1. If you are using MySql as your database platform, you'll need to check how boolean fields are represented. Review the structure of your current `BLC_ADDRESS` table. If the `IS_ACTIVE` column is of type BIT, then you are using the old way of representing boolean fields in MySql. If the type is TINYINT, then you can ignore this item.

2. If your boolean columns are represented as BIT, then you have 2 choices for Broadleaf 3.0 compatibility:
    - You can convert all boolean field columns in your Broadleaf database schema from BIT to TINYINT, **OR**
    - You can use `org.broadleafcommerce.common.dialect.Broadleaf2CompatibilityMySQL5InnoDBDialect` as your Hibernate dialect (this custom dialect takes care of referencing boolean fields as type BIT, rather than TINYINT)

3. There are no known issues with PostgreSql, Sql Server or Oracle.

-------------

**Item**: Make sure locale settings are up-to-date

1. Review the contents of the `BLC_LOCALE` table. One of the locales should be marked as default.

2. Make sure the default locale is your desired locale, as this can impact price display on your site

3. For example, if `en` is the default locale, you may want to add a new locale with code `en_US` for US English and make it the default instead.

-------------

**Item**: Make sure existing orders are compatible

1. Add a value to the `LOCALE_CODE` column for all orders in the `BLC_ORDER` table. For example, use `en_US` for US English.

-------------

**Item**: Additional admin updates

1. Remove the `templates` directory from `admin/src/main/webapp/WEB-INF`

-------------

**Item**: Property file updates

1. Remove the `use.jrebel.compatibility.mode` property as it is no longer used.
2. Add `thymeleaf.view.resolver.cache=true` to common-shared.properties and `thymeleaf.view.resolver.cache=false` to development-shared.properties

## Considerations

**Admin Customization Considerations (If your current implementation has admin customizations)**

1. GWT has been phased out and is no longer supported for admin UI/functionality customization.
2. Logical portions of the admin are broken up into Modules, which themselves contains sections.
3. Modules are represented in the `BLC_ADMIN_MODULE` table and sections are represented in the `BLC_ADMIN_SECTION` table.
4. @AdminPresentation annotations in the Broadleaf domain classes support most of the functionality observed in the admin.
5. For simple extended properties, it's possible that you're entity extensions may work as they are in the new admin without any additional @AdminPresentation annotation tweaking.
6. For collection/map fields in your entity extensions, you will need to use one of the admin presentation collection annotations. Refer to the [source code for ProductImpl](https://github.com/BroadleafCommerce/BroadleafCommerce/blob/broadleaf-3.0.0-GA/core/broadleaf-framework/src/main/java/org/broadleafcommerce/core/catalog/domain/ProductImpl.java) for a variety of concrete usage examples.
7. Spring MVC is employed to drive most of the plumbing - specialized controllers can be used to achieve specific results (e.g. see AdminOrderController in the Broadleaf source).

**Order Pricing Considerations**

1. In previous releases, it was possible for order items to be split in the order when promotions were applied. This generally occurred as the result of a Buy-One-Get-One-Free promotion where only part of the total quantity for an item qualified for a discount. In such a case, a new discounted Order Item was created with the smaller quantity and the quantity for the regularly priced item was decremented - essentially "splitting" the item.
2. The "splitting" practice was error prone, as various parts of the order had to be update to compensate for the split (e.g. fulfillment group items had to be updated).
3. In version 3.0, we have done away with the Order Item splitting concept in favor of OrderItemPriceDetails.
4. OrderItemPriceDetails allows a single order item to have multiple prices for multiple quantities. This solves the requirement for discounting several of an order item's quantity, while not changing the quantity of the order item itself.
5. As a result, a call to OrderItem.getPrice() now returns an average of the price details for an item.
6. Depending on how order item pricing is displayed on your site, this change could have an impact on what your users see and your site should be thoroughly tested after the upgrade as a result.

**Offer Considerations**

1. The MVEL generated for offers in version 2.2 may be incompatible with the new 3.0 rule builder UI.
2. Incompatible rules will still function in the system, but will be displayed in the admin page as immutable,raw MVEL.
3. If you wish to change the rules for an incompatible offer, you'll need to disable the incompatible offer and create a new offer that matches your desired rules and configuration.

**Translation Considerations (if your site requires multiple language support)**

1. Broadleaf 3.0 offers new field-level translation in the admin (denoted by a globe icon - see product name for an example).
2. To take advantage of this new translation service, consider moving your catalog translations to the `BLC_TRANSLATION` table.
3. Take a look at the 3.0 demo site `BLC_TRANSLATION` data for examples. ([Sample translation data](https://github.com/BroadleafCommerce/DemoSite/blob/broadleaf-3.0.0-GA/core/src/main/resources/sql/load_catalog_i18n_data_ES.sql))

**Heat Clinic Considerations**

Please note that this migration documentation is to be used as a guide in migrating any generic Broadleaf Commerce application to version 3.0. We do not cover things that we might have changed in our starter Heat Clinic project, such as miscellaneous CSS updates, etc. For example, to take advantage of the PhoneImpl Java class, we changed the Heat Clinic checkout's billingInfoForm.html. These kinds of specialized changes in our sample application are not covered as part of this guide. 

If you would like to see an absolutely comprehensive list of all changes that were made to our sample application between 2.2 and 3.0, you can utilize [this GitHub branch compare link](https://github.com/BroadleafCommerce/DemoSite/compare/BroadleafCommerce-2.2.x...admin3).