I am running a application based on the Community version of Broadleaf Commerce demo site (hot sauce).

To experiment with CI and deployment options, we have converted the stock spring boot packaging (jar) to war following the broadleaf and spring documentation.

After conversion, the application will start normally, but it seems that some database (JPA) interactions have been broken (errors on search and DB updates).

I have a few related questions:

Is there additional configuration or considerations required to initialize/access JPA (via Hibernate) resources when converting from jar to war above what is specified in the spring documentation above?

Specifically related to the error I am seeing (copied below) regarding JPA criteria path, I found this SO post suggesting that it might be an implementation problem. But back to question #2, if that is the case, why would it matter which way I ran the application if it's a code issue?

To which runtime (e.g. Tomcat, Weblogic, JBoss, Websphere) you are deploying your war file to? Also, could you please do a mvn dependency:tree on your project and make a list of all the dependencies - of course you would understand what those dependencies do. Next go to your app server/servlet container's configuration and figure out if it is pre-pending any class loaders that load different versions/implementations of your intended dependencies. Let us know. If everything is same and your runtime is not polluting your application's classpath, then we ought to investigate further.
– Arun PatraNov 9 at 6:25