Page 1 of 1

Broadleaf without spring

Posted: Wed Feb 02, 2011 11:05 pm
by idont
Hi,
Though I have been programming JEE I have yet to work with Spring. I am curious if I can use broadleaf without using Spring Beans, meaning can I build the system in my Java Code by directly calling constructors etc.... Is there any source material for how this might be done? I do appreciate any help.

Btw, I am trying to use BroadLeaf with Wicket if anyone has any experience with both I would like to know any thoughts or considerations... Thanks in advance.

Matthew

Re: Broadleaf without spring

Posted: Wed Feb 02, 2011 11:39 pm
by jefffischer
Broadleaf is based on Spring down to the foundation. While I suppose it's possible to supplant the dependency injection and transaction support (among other things) that it provides, I wouldn't want to try to unravel it all and replace it. I would say you're most definitely better off learning the basic Spring you need to work with Broadleaf rather than trying to run Broadleaf without it.

Re: Broadleaf without spring

Posted: Thu Feb 03, 2011 7:02 pm
by idont
I really appreciate the quick response. Okay, I will look into Spring, I should probably learn it, I have been putting it off for a while now.

Thank you,
Matthew

Re: Broadleaf without spring

Posted: Fri Feb 04, 2011 3:45 pm
by idont
Hi,
So I have been learning Spring, quite interesting, I see a lot of ideas have been accepted like IoC for Ejb, so it wasn't too much new to learn. At any rate, I do want to check a few things:

1). I can use BroadLeaf without SpringMVC (which did seem implied by the documentation).
2). I can use BroadLeaf to manage multiple stores on one database?
3). From the documentation it seems only credit cards are handled through cyber source, but there is code for paypal in BroadLeaf, is that functional? Plans for google-checkout in the future?


Well I guess those are my main questions, can't think of much else right now... Thank you so much for your help, I am quite curious about #2, if anything like that is feasible.

Matthew

Re: Broadleaf without spring

Posted: Fri Feb 04, 2011 4:08 pm
by jefffischer
1) Broadleaf is agnostic about the presentation layer. You can use whatever presentation layer approach you like as long as you can communicate with the Broadleaf Spring service layer. In addition, it's on our roadmap to finalize our webservice approach, which would expose other possibilities for communication...

2) Unfortunately, the current database schema and supporting code support a single store only. Building out the schema to support a "multi tenant" architecture is also on our feature roadmap.

3) The Broadleaf payment architecture allows for pretty much any time of payment (and in any combination per order :D ) given that there is a payment module to support the transaction. For example, from a CyberSource perspective, we have elaborated three types of payment represented in the CyberSourceMethodType enumeration (Credit Card, Bank Draft and PayPal). CyberSource support these (and likely more) through their API, but we have currently only built out support for credit card payment. Bank Draft and PayPal still need to be built out as Broadleaf payment services under the CyberSource payment module umbrella.

Google Checkout is definitely something we've thought about, but the requirements and payment flow are different enough that it will be a bit of a larger effort than the others. Still important, though.

As you can tell, there's still work to be done building out some of these integrations (payment, shipping, tax). We currently have functional support for CyberSource credit card payment, CyberSource tax calculation and USPS shipping pricing. We definitely anticipate tackling others, but at the moment, we're focusing all our effort on the 1.5 release and the completely re-done administrative platform.

If you're curious about upcoming releases and features, take a look at our high-level product roadmap at:

http://www.broadleafcommerce.org/jira/s ... dmap-panel

Re: Broadleaf without spring

Posted: Sun Feb 06, 2011 8:35 pm
by idont
1). Perfect.
2). That is funny I looked at the road-map and didn't realize multi-tenant was that, but now I get it. I have a feeling I will be able to enable it myself then since I am not interested in multi-tenant in the sense that they are sharing users/products or one administrator.... Rather I just want to use one database (sql) - maybe same schema but not necessary - to the point it behaves almost if there were separate instances, but having only one so... I should be able to figure out some way of adding a column or keeping more then one persistent layer, not sure. Hopefully it will not be too complicated. I will probably start with one store of course and when I am more comfortable expand.

3). That is nice, even if it is not available immediately, it is nice that it is something being worked on.

I must say, I am quite impressed with BroadLeaf.