Hi Andrea Can you elaborate what you mean by "...stores very comoplex data on JCR..." and "...flexible solution"?
Concerning the state of the module: It is currently being worked on to be moved to Freemarker/STK. Regards, -will On 21.02.2011, at 16:06, 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? > > Thank you. > Best regards. > Andrea ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
