Yes it manages inventory, order processing, payment gateways, users etc... So all of that is done with a nice admin interface already to go. I'm just looking at building some front end component that use it's api for actual store front. Their own default storefront is JSP based and they have an example of another one which I think was flash.

Got the rough outline of a category tree, product list, cart and search box done today to see how hard it was going to be and seems quite workable.

Per Lundholm wrote:
When you wrote "shopping cart", I assumed it was only the widget which
presents what the customer bought and some mechanism for keeping that
in the session. KonaKart seems to be a lot more than that.


On Tue, Aug 3, 2010 at 2:35 AM, Steve Coughlan
<> wrote:
I've been looking for a shopping cart solution that I can properly integrate
with wicket.  There's been a few threads on this list where people have
indicated they were building one but as far as I know nothing has ever

I don't really want to build to whole engine from scratch so I've been
looking around and come across konakart.  It's partially open source.
 Meaning the engine itself is closed but it has a complete (and well
documented) integration layer.  I think this would be a good solution
because all the backend functionality is there along with a nice admin

The interface is either Java or SOAP (one line of code to switch between the
two) which means you can run your cart engine on another server if you want.

So what I'm proposing is build a set of front-end wicket components.  I'd
prefer a fully open source solution but in the free java space this seems to
be the easiest solution I can find.  I really don't have time to build an
engine from the ground up.

So before I get going I just wanted to bounce it off the community and see
if anyone can think of a better solution?

I only just come across brix and I'm still trying to get my head around it.
 Any comments on whether  I should make this brix centric or pure wicket?

p.s. If I do build these components then I will release them as LGPL...

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to