There are lots of different types of dependencies. Pulling out any of
the application components in OFBiz is technically possible, but
would require a lot of work that becomes a variation on the code base
that you'd have to maintain, and is therefore generally a very bad
idea that doesn't hit you in the head until some time down the road
when you realize that maintaining 700,000 lines of code on your own
really sucks and that you'd really like to work with the community to
keep things up to date and take advantage of fixes and feature
additions other people are doing.
I'd recommend not removing components. Leave the data model and all
services in place. You can comment out ECA rules to turn off parts of
the higher level business processes and you can leave webapps
unmounted that you are not using. Those are both pretty safe for
slimming down an OFBiz instance. Otherwise, I'd have a very long hard
look at the return on investment for removing stuff.
What would you really get out of it anyway?
I've talked with a lot of people who want to do this and they really
have it all backwards. They think that if they slim down OFBiz they
will have less to learn and deal with. The fact of the matter is that
the slimming down process drops them right into the frying pan and
they are then forced to deal with hundreds of entities, services, and
so on that they otherwise wouldn't even have to know about or touch
(unless something went wrong, and then they could appeal to the
community or hire someone with experience to fix that for them).
-David
On Nov 15, 2006, at 12:34 PM, Anders Hessellund wrote:
Hi,
What sorts of dependencies? I guess I'm trying to narrow the scope as
there are so many different things...
Specifically, I am concerned with dependencies between different ofbiz
modules. How can I for instance determine what the applications/
accounting
module depend on, if I want to deliver a stripped-down ofbiz
deployment?
-- Anders
-David
On Nov 12, 2006, at 4:38 PM, Anders Hessellund wrote:
Hi,
how are dependencies among ofbiz components expressed? Is there a
single
place to declare dependencies on other components, or can the
dependency-related code/xml be scattered around in the internals
of a
component?
-- Anders
