I have done two KonaKart + Magnolia integrations using the KonaKart Java API and Blossom. The end result is you have pages like this in Magnolia that use Blossom Templates to integrate w/KonaKart using the Java API:
/shop + /shop/cart/add + /shop/cart/view + /shop/cart/update + /shop/cart/remove + /shop/checkout/addresses + /shop/checkout/shipping + /shop/checkout/payment + /shop/checkout/confirm etc. Depending on your particular site's needs you probably also have pages or data nodes for each physical product. We built all of the above by reviewing the existing KonaKart Struts application and the KonaKart documentation (Online and Javadocs). No offense to the KonaKart team (They actually provide quite a bit of documentation) but be forewarned that since NOT ALL source code is available you will spend some writing and testing in trial and error fashion. I had to do some "debugging" through Java bytecode since not all the source is available. I like KonaKart but to be honest we are going to consider other options for our next site simply because we want to be working with 100% open source projects and KonaKart is not 100% open source. Here is where we are heading: http://www.broadleafcommerce.org/ The biggest problem with any solution is going to be customizing it to fit your needs. We have done two now, one more traditional site selling home products and another that literally sells Ice Cream. The Ice Cream store had several unique needs that probably no existing ecommerce platform provides out of the box! Tom On Feb 21, 2011, at 9:50 AM, Giancarlo F. Berner wrote: > - Solution 1: If you want a quick-and-dirty e-Shop, this works fine. > Customization is a little tricky in the beginning, but once you understand > that the KK paragraph references a JSP in /WEB-INF, you can adapt these JSPs > to fit your design. But if you want full customized multi-shop solution you > will byte dust (e.g. I had to write a text/image paragraph with a control for > each language) > - Solution 2: If you know you will need e-Shops in the future I would look > into building some WSDL type interface (e.g. using SOAP). There is a > "OpenCMS" module you might want to study. Since you will put a lot of effort > in the interfacing of both, the KK and MG world, you will have to invest > quite some time. The result is though a very flexible solution. Another > option is to communicate with KK via RMI. Any way, I don't like the idea of > having to interact to a proprietary system this way. > - Solution 3: My personal favorite. While the approach of using the > underlying JCR to store the data is hype, the solution per se is still under > construction. A first version is available. If that works, give it a try! > > Solution 4: My favorite solution is to build a JCR based e-Shop backend, > providing an API to build the front-end. The idea is that you can integrate a > JAR either via OSGi or simply drop it into any APP server and it you can > build Mg paragraphs using the API. The solution will be available for any JCR > based systems (e.g Mg, Day Communique, etc.). HOWEVER: While I am almost done > with the architecture, development/testing did not start yet, so it will NOT > BE AVAILABLE until around end of year. > > To summarize: Be prepared to get your hands dirty! > > /giancarlo > > On Feb 21, 2011, at 7:06 AM, Andrea Castelli wrote: > > Hi everybody. > I'm evaluating different solutions to build a shop online on Magnolia. > I analyzed the following: > Konakart + konakart-module (by Headwire) > Konakart API and integration made by myself. > Magnolia Shop Module. > I would like to choice solutions 1 or 3 because seems that I should work > less. <35C.png> > > But: > Solution 1 is built upon Struts and the preferred MVC of Magnolia is Spring. > (I don't like to spend my time in a framework that is not on the main road) > The code seems to be not a very multisite by default. A change to the basic > Magnolia chain filter is required (I don't like to change the default > behaviour of Magnolia). What do you think about it? But it is the only one > ready to start.(This is a great value). > Solution 2 is based on the API of Konakart. Anyone has experience on it? Any > advice? > Solution 3 stores very complex data on JCR, I need a flexible solution so I > don't investigate further and I don't know the state of the art. > Did I miss something? > Can you help me in this market evaluation? -- Tom Duffey [email protected] 414-915-3915 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
