Updating to New 3.0 BETA versions

Suggest features you would like to see in Broadleaf Commerce

Moderator: jocanas

phillipuniverse
Team Member
Team Member
Posts: 1563
Joined: Tue Dec 20, 2011 12:11 pm

Updating to New 3.0 BETA versions

Postby phillipuniverse » Thu Jun 06, 2013 11:04 am

If you are currently targeting a Broadleaf 3.0 beta version, you will probably want to keep your heat clinic up to date. Luckily, GitHub has an easy-to-view diff between tags, branches and commits.

For instance, say that you downloaded the 3.0.0-BETA2 workspace, and now you want to upgrade to BETA3. The first step would be to change the Broadleaf version in your pom.xml:

Code: Select all

<blc.version>3.0.0-BETA3</blc.version>


But you still might run into compilation errors because of things that have changed in our DemoSite to deal with changes in the Broadleaf framework. In this scenario, the diff between BETA2 and BETA3 can be found via this link:

https://github.com/BroadleafCommerce/De ... .0.0-BETA3

If you instead want to move to target a SNAPSHOT version of 3.0 (3.0.0-SNAPSHOT), you can get the heat clinic diff by going to:

https://github.com/BroadleafCommerce/De ... 2...admin3

In general, you can get these diffs by using a URL of the following form:

Code: Select all

https://github.com/BroadleafCommerce/DemoSite/compare/<branch/tag/commit SHA>...<branch/tag/commit SHA>


We are tagging commits in DemoSite for new versions of the Broadleaf 3.0 BETA so that this process is as easy as possible.

anikanchan
Junior
Junior
Posts: 33
Joined: Wed Aug 08, 2012 12:07 am

Re: Updating to New 3.0 BETA versions

Postby anikanchan » Tue Jun 11, 2013 10:06 pm

I want to create my application using latest broadleaf framework 3.0-BETA3 (without using DemoSite). Is there any tutorial/guideline/documentation for that?
- Anikanchan
Advisor
SRInfocom

phillipuniverse
Team Member
Team Member
Posts: 1563
Joined: Tue Dec 20, 2011 12:11 pm

Re: Updating to New 3.0 BETA versions

Postby phillipuniverse » Tue Jun 11, 2013 10:09 pm

This is not something we would recommend. We recommend all sites use DemoSite as a starting point since it contains configurations that most (if not all) Broadleaf sites will need.

We do not currently have any documentation for starting a new site completely from scratch. The DemoSite heat clinic is actually the replacement for the old Maven archetype.

anikanchan
Junior
Junior
Posts: 33
Joined: Wed Aug 08, 2012 12:07 am

Re: Updating to New 3.0 BETA versions

Postby anikanchan » Wed Jun 12, 2013 8:06 am

I have tried using DemoSite version 3 as well but problem I am facing there is that other modules are not at version 3 level and their integration is getting challenging.
- Anikanchan
Advisor
SRInfocom

anikanchan
Junior
Junior
Posts: 33
Joined: Wed Aug 08, 2012 12:07 am

Re: Updating to New 3.0 BETA versions

Postby anikanchan » Tue Jun 25, 2013 7:43 pm

If BL recommends using DemoSite for starting point, what is the point of framework and all different modules. Is there anyway, we users can contribute with documentation?
- Anikanchan
Advisor
SRInfocom

bpolster
Team Member
Team Member
Posts: 137
Joined: Fri Nov 20, 2009 1:40 am

Re: Updating to New 3.0 BETA versions

Postby bpolster » Wed Jun 26, 2013 9:11 pm

Anikanchan,

1. What modules are you trying to integrate? We still have work to do to bring over many of the 2.x modules and are prioritizing them based on immediate needs.

2. We are working on a way to have users contribute documentation. It's actually a really clever idea from a couple of our developers that will leverage GitHub. You'll here more about it soon.

3. Also, I'll amend what Phillip said as far as us "recommending" that projects use the DemoSite. We believe it is the best place to start as you are learning and prototyping the system. We will also keep it up to date and provide module documentation going forward that shows how a module can be added to the DemoSite. That being said, I personally would remove most DemoSite specific code, assets, etc. from my actual production code. This shouldn't be a terribly difficult exercise and we will continue to work on improving the documentation in this area.
Brian Polster
Broadleaf Commerce
bpolster@broadleafcommerce.org

anikanchan
Junior
Junior
Posts: 33
Joined: Wed Aug 08, 2012 12:07 am

Re: Updating to New 3.0 BETA versions

Postby anikanchan » Thu Jun 27, 2013 8:08 pm

Brian,

Thanks for your note. I am trying to include inventory module to demo site 3.0. Due to drastic changes to admin architecture, I do not want to start with demosite-inventory accelerator.

Regards,

Anikanchan
- Anikanchan
Advisor
SRInfocom

anikanchan
Junior
Junior
Posts: 33
Joined: Wed Aug 08, 2012 12:07 am

Re: Updating to New 3.0 BETA versions

Postby anikanchan » Fri Jul 05, 2013 11:55 pm

I started with DemoSite 3.0 version and followed steps from http://docs.broadleafcommerce.org/dev/Inventory.html to add inventory module. I did not modify the workflow.

Here is the error that I see when I start the jetty-demo task for site module:

[artifact:mvn] [ERROR] 00:37:52 SchemaExport - HHH000231: Schema export unsuccessful
[artifact:mvn] org.hibernate.tool.hbm2ddl.ImportScriptException: Error during statement execution (file: '/sql/load_admin_users.sql'): INSERT INTO BLC_ADMIN_PERMISSION_ENTITY (ADMIN_PERMISSION_ENTITY_ID, CEILING_ENTITY, ADMIN_PERMISSION_ID) VALUES (230, 'org.broadleafcommerce.core.inventory.domain.FulfillmentLocation', 64)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.SchemaExport.importScript(SchemaExport.java:451)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:378)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:304)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:293)
[artifact:mvn] at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:498)
[artifact:mvn] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1743)
[artifact:mvn] at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
[artifact:mvn] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
[artifact:mvn] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
[artifact:mvn] at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
[artifact:mvn] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:288)
[artifact:mvn] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1547)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1485)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:524)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:461)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
[artifact:mvn] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
[artifact:mvn] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
[artifact:mvn] at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1117)
[artifact:mvn] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:922)
[artifact:mvn] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
[artifact:mvn] at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389)
[artifact:mvn] at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294)
[artifact:mvn] at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112)
[artifact:mvn] at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766)
[artifact:mvn] at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406)
[artifact:mvn] at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758)
[artifact:mvn] at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242)
[artifact:mvn] at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233)
[artifact:mvn] at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701)
[artifact:mvn] at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475)
[artifact:mvn] at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:256)
[artifact:mvn] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
[artifact:mvn] at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
[artifact:mvn] at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167)
[artifact:mvn] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
[artifact:mvn] at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
[artifact:mvn] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
[artifact:mvn] at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90)
[artifact:mvn] at org.eclipse.jetty.server.Server.doStart(Server.java:272)
[artifact:mvn] at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
[artifact:mvn] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
[artifact:mvn] at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:511)
[artifact:mvn] at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:364)
[artifact:mvn] at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:516)
[artifact:mvn] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[artifact:mvn] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[artifact:mvn] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[artifact:mvn] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[artifact:mvn] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[artifact:mvn] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[artifact:mvn] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[artifact:mvn] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[artifact:mvn] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
[artifact:mvn] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[artifact:mvn] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[artifact:mvn] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[artifact:mvn] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[artifact:mvn] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[artifact:mvn] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[artifact:mvn] at java.lang.reflect.Method.invoke(Method.java:597)
[artifact:mvn] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[artifact:mvn] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[artifact:mvn] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
[artifact:mvn] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[artifact:mvn] at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
[artifact:mvn] Caused by: java.sql.SQLIntegrityConstraintViolationException: integrity constraint violation: foreign key no parent; FK23C09E3DE88B7D38 table: BLC_ADMIN_PERMISSION_ENTITY
[artifact:mvn] at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
[artifact:mvn] at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
[artifact:mvn] at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
[artifact:mvn] at org.hsqldb.jdbc.JDBCStatement.executeUpdate(Unknown Source)
[artifact:mvn] at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.DatabaseExporter.export(DatabaseExporter.java:64)
[artifact:mvn] at org.hibernate.tool.hbm2ddl.SchemaExport.importScript(SchemaExport.java:446)
[artifact:mvn] ... 68 more
[artifact:mvn] [ERROR] 00:37:53 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible
[artifact:mvn] [ WARN] 00:37:53 Ejb3Configuration - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
[artifact:mvn] [ERROR] 00:37:54 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible
[artifact:mvn] [ WARN] 00:37:54 Ejb3Configuration - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
[artifact:mvn] [ WARN] 00:37:58 CoreContainer - Log watching is not yet implemented for log4j
[artifact:mvn] [ WARN] 00:37:58 SolrCore - New index directory detected: old=null new=/var/folders/fv/390t4lhd72v27ps7x0hw38000000gn/T/anikanchan/solrhome/core0dir/data/index/
[artifact:mvn] [ WARN] 00:37:58 SolrCore - [primary] Solr index directory '/var/folders/fv/390t4lhd72v27ps7x0hw38000000gn/T/anikanchan/solrhome/core0dir/data/index' doesn't exist. Creating new index...
[artifact:mvn] [ WARN] 00:37:59 SolrCore - New index directory detected: old=null new=/var/folders/fv/390t4lhd72v27ps7x0hw38000000gn/T/anikanchan/solrhome/core1dir/data/index/
[artifact:mvn] [ WARN] 00:37:59 SolrCore - [reindex] Solr index directory '/var/folders/fv/390t4lhd72v27ps7x0hw38000000gn/T/anikanchan/solrhome/core1dir/data/index' doesn't exist. Creating new index...
[artifact:mvn] 2013-07-06 00:38:01.958:INFO:oejsh.ContextHandler:started o.m.j.p.JettyWebAppContext{/,file:/Users/anikanchan/git/galagz/galagz-site/target/galagz/},file:/Users/anikanchan/git/galagz/galagz-site/target/galagz/
[artifact:mvn] 2013-07-06 00:38:02.038:INFO:/:Initializing Spring FrameworkServlet 'galagz'
[artifact:mvn] 2013-07-06 00:38:04.503:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8080
[artifact:mvn] 2013-07-06 00:38:04.631:INFO:oejus.SslContextFactory:Enabled Protocols [SSLv2Hello, SSLv3, TLSv1] of [SSLv2Hello, SSLv3, TLSv1]
[artifact:mvn] 2013-07-06 00:38:04.631:INFO:oejs.AbstractConnector:Started SslSelectChannelConnector@0.0.0.0:8443
[artifact:mvn] [INFO] Started Jetty Server
- Anikanchan
Advisor
SRInfocom

jskorton
Beginner
Beginner
Posts: 17
Joined: Tue Jun 25, 2013 3:26 pm

Re: Updating to New 3.0 BETA versions

Postby jskorton » Wed Jul 17, 2013 1:26 pm

Anikanchan,

From your error:

"artifact:mvn] org.hibernate.tool.hbm2ddl.ImportScriptException: Error during statement execution (file: '/sql/load_admin_users.sql'): INSERT INTO BLC_ADMIN_PERMISSION_ENTITY (ADMIN_PERMISSION_ENTITY_ID, CEILING_ENTITY, ADMIN_PERMISSION_ID) VALUES (230, 'org.broadleafcommerce.core.inventory.domain.FulfillmentLocation', 64)"

It seems like the primary keys might have to change. Check the state of your database/import.sql files.

http://docs.broadleafcommerce.org/dev/Inventory.html - Ensure that the proper admin permissions are associated
Joshua Skorton
Broadleaf Commerce
jskorton@broadleafcommerce.com

hourieh
Newbie
Newbie
Posts: 4
Joined: Tue Sep 03, 2013 12:53 am

Re: Updating to New 3.0 BETA versions

Postby hourieh » Tue Sep 03, 2013 1:00 am

Hello there
I have a serious problem with broadleaf-3.1.0-ALPHA1.it couldn't make WAR file I found why it couldn't but I don't know how to fix it.during broadleaf-3.1.0-ALPHA1 in admin modul you see 3 sub modul for making WAR file via maven we need one of this sub modul has a pakage for making war file but all of these pakages are jar and ther is no pakage to make a war file I don't know how to fix it and how to make a war file
I look forward to hearing from you
thanks


Return to “Suggested Features”

Who is online

Users browsing this forum: No registered users and 1 guest