为什么选择 Broadleaf Commerce 而不是 Magento 或 ZenCart？
我有一个用 java-spring-hibernate 制作的网站，我们从头开始制作，它显示了产品目录，我有它的逻辑。我还可以使用我们在 Flex 中创建的管理员来管理内容和产品/类别。我们可能不应该这么麻烦，因为那里有这么多的厘米，但已经完成了。该站点使用 jstl 将在 Flex 中管理的内容呈现在 html 中。
现在我想向其中添加电子商务，因为我们必须将所有付款、发货、订单逻辑添加到管理员和前端（购物车/用户）。然而，既然已经有了像 magento store 这样的东西，我想也许我应该切换并让我美丽的应用程序死掉：/。当我研究时，我偶然发现了阔叶商务，这是一个用 Flex-Spring-Hibernate 制作的电子商务后端。它相对较新，应该有一个活跃的开发团队。所以我想我的问题是，为什么？如果有这么多开源商务解决方案，他们会在开发方面做出这样的努力吗？我的意思是你仍然需要为用户端构建 GUI。它们与magento有什么区别，有什么优点？我应该尝试与阔叶集成吗？那么保留我喜爱的旧应用程序有哪些资产？
I have a site made in java-spring-hibernate we made our self from scratch, it shows a catalog of product and i have the logic for it. I can also manage content and product/categories with it with an administrator we have made in flex. We probably shouldn´t have gone to all the trouble since there are so many cms out there, but what's done it's done. The site renders the content managed in flex in html with jstl.
Thing is now i want to add a ecommerce to it, for that we would have to add all the payment,shipment, orders logic to the administrator and the front end (cart/user). How ever, since there are already things like magento store, i was thinking maybe i should switch and leave my beautiful app to die :/. As i was researching i stumbled upon broadleaf commerce which is an ecommerce back end made in flex-spring-hibernate. It´s relatively new and it supposed to have an active development team. So i guess my question is, Why? if there are so many opensource commerce solutions do they make this kind of effort in developing ? i mean you still have to build the GUI for the users side. Whats their difference with magento, what are the pros ? should i try to integrate with broadleaf ? what are the assests oder then keeping my loved old app ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
首先我要表明自己是 Broadleaf Commerce 的员工，所以我可能有些偏见。开发Broadleaf的原因确实与平台本身有很大关系。如果您查看现有的开源电子商务解决方案，您会发现其中有很多解决方案是正确的。然而，当您开始通过各种参数（包括 Java、Spring、Hibernate）过滤它们时，列表就会变得非常小。我们的目的始终是针对当今的企业用户推出一个引人注目的电子商务平台。考虑到这个主题，我们知道我们必须使用 Java、Spring 和 Hibernate。这是许多开发社区（尤其是企业领域）首选的核心技术堆栈。此外，为了满足这些用户的复杂领域和集成需求，我们从头开始设计系统时就考虑到了可扩展性。我们将可扩展性视为您日常练习的面向对象编程技术的自然扩展。这意味着利用 Hibernate 扩展和域多态性的强大功能，以及覆盖、调整或完全替换代码库中每个服务、DAO 和实体的能力。我们的配置也是可扩展的，并且超越了标准 Spring 应用程序上下文覆盖，提供了更多配置合并功能，使我们能够消除一些额外的 Broadleaf 配置复杂性，以便您可以专注于对您的应用程序重要的配置。因此，虽然我们的软件和其他软件的最终结果可能相似，但我们相信，决定采取什么途径来实现最终目标是一个重要的决定，而 Broadleaf Commerce 提供了一种强大而灵活的方式来实现这一目标。
我觉得我还应该简单提一下，既然您在上面提到了 Flex，我们目前正在开发 1.5 版本，其中包括一个基于 GWT 的重新设计的管理应用程序，它将取代我们当前基于 Flex 的管理应用程序。这一选择使我们能够将核心平台中已经包含的可扩展性主题传播到我们的管理平台。新的管理将通过面向对象的编程范例提供与开发人员在核心平台中已经享受到的相同的覆盖和替换灵活性。此外，管理应用程序会自动识别您的实体扩展，并将您的附加字段包含在管理界面中，而无需代表您进行任何编码工作。管理界面还尊重实体多态性，并将根据每种类型调整编辑界面（想象一下具有书籍和电影两种扩展形式的媒体产品 - 尽管它们都是媒体实体，但它们都有独特的字段和管理界面尊重这一区别）。我们还致力于 1.5 的变更集和其他一些有趣的功能。我们的目标是四月份左右开始发布里程碑版本，敬请关注更多信息。
Let me start off by identifying myself as an employee of Broadleaf Commerce, so I may be somewhat biased. The reason for developing Broadleaf really has everything to do with the platform itself. If you look at the open source e-commerce solutions out there, you are correct in that there are a number of them. However, when you start to filter them by various parameters, including Java, Spring, Hibernate - the list becomes very small. It was always our intent to come up with a compelling e-commerce platform targeted at today's enterprise users. With that theme in mind, we knew we had to go with Java, Spring and Hibernate. This is the core technology stack that is preferred by much of the development community, especially in the enterprise segment. Also, to satisfy the complex domain and integration requirements of these users, we designed the system from the ground up with extensibility in mind. We think of extensibility as a natural extension of the Object Oriented programming techniques you already practice daily. This translates into leveraging the power of Hibernate extension and polymorphism for the domain, as well as the ability to override, tweak or completely replace every service, DAO and entity in the codebase. Our configuration is also extensible, and goes beyond standard Spring application context override to provide more configuration merge capabilities that allow us to pull away some of the additional Broadleaf configuration complexity so you can focus on the configuration that matters for your app. So while the end results may be similar between our software and others, we believe the decision on what path to take to achieve that end goal is an important one and Broadleaf Commerce offers a powerful and flexible way to get there.
I feel I should also briefly mention, since you mention Flex above, that we are currently in development of our 1.5 release, which includes a re-worked administrative application based on GWT that will replace our current Flex-based admin. This choice has allowed us to propagate the same theme of extensibility that we already embrace in the core platform to our administrative platform. The new admin will offer the same flexibility for override and replacement through Object Oriented programming paradigms that developers already enjoy in the core platform. In addition, the admin application automatically recognizes your entity extensions and includes your additional fields in the admin interface without any coding effort on your behalf. The admin interface also honors entity polymorphism and will adjust the editing interface according to each type (think of a media product that has two extensions in the form of book and movie - even though they are both media entities, they each have unique fields and the admin interface honors this distinction). We're also working on changesets and some other interesting features for 1.5. We're targeting milestone releases beginning around April, so stay tuned for more.
Spring 和 Hibernate 缺少的是适当的数据模型和 erp 应用程序，因此每个人都开始构建自己的。
我们都在相同的应用程序和框架上共同构建。
这就是 OFBiz：框架以及适当的数据模型和应用程序。你知道最好的部分吗？它不是由一家公司控制的，而是由世界上最大的开源基金会控制的：由所有大型 IT 公司赞助的 Apache 基金会。
任何开始实施自己的电子商务 erp 的人都应该重新考虑。
有关 Apache ofbiz 的更多信息？
http://www.ofbiz.info
http://ofbiz.apache.org
问候，
汉斯
What Spring and Hibernate are missing is a proper datamodel and erp application so everybody starts building their own.
We are all building together on the same application and framework.
That is just OFBiz: framework and a proper datamodel and application. You know the best part? It is not controlled by a single company but by the biggest open source foundation in the world: The Apache foundation sponsored by all large IT companies.
Anybody starting his own implementation of either erp of ecommerce should really reconsider.
More info on Apache ofbiz?
http://www.ofbiz.info
http://ofbiz.apache.org
Regards,
Hans
有一个用于 Magento API 的 Java 连接器，称为 Magja 。
注意：2012年之后不再支持！
There is one Java Connector for Magento's API called as Magja.
Note: No support after 2012!