let me expand on that. Backend: catalog is used to display the products. content is used to display forums and blogs. Promos is generated by the catalog to be diplayed. reviews are from the content application. configurable products use the catalog and manufacturing. Cart is in the order application. Login ability and info about the customer is in the Party application. the login code is in the framework. So you see there is not much in the ecommerce but a shell to display all this info from other applications and the framework.
BJ Freeman sent the following on 10/16/2008 5:03 PM: > > David Legg sent the following on 10/16/2008 4:21 PM: >> Hi BJ, >> Some people have sounded surprised that people would even consider not >> using the built-in ecommerce web app. Whilst I think the OfBiz >> framework is very elegant you can't expect everyone to drop their >> existing frameworks just to display a product list and a shopping basket! > > yes, considering the ecommerce portion is just a shell without the backend. > > > I don't see what you will get by trying to use the ecommerce apps with > another backend, unless that backend supplies the necessary support > that the ofbiz backend does. > > In that case it would be less effort then to use the ecommerce as a > model but do the coding in same model as the backend you are working with. > IMHO > :D > >
