On Nov 13, 2009, at 11:10 AM, Christopher Snow wrote: > When I tried to remove the unwanted components, I can into dependency > problems. A modular approach to using the components such as maven would > stop the developer having to manually work out dependencies to remove > components. >
The best ways to do this are: a) assigning proper permissions to users so that only the relevant applications are shown OR b) remove the "webapp" elements from the ofbiz-component.xml files > Leaving the unwanted components in place even though they don't get used > makes DBA's and support people twitchy, asking questions like "why are all > those tables created even though they aren't used?" > They are there because sooner or later the customer may discover that they need them (by experience this happens very often) and it is easier to configure the data to use them. When we consider the ERP "applications" it doesn't make much sense to consider them independent because they model the real world and in the real world they are very inter dependent. On the other hand, if you want to build an application from scratch and just use OFBiz framework, the best way to go is to remove the "applications" and "specialpurpose" folders. It will work even if we still have to clean up a few things (for example it would be cool to have a user interface in Webtools to manage users and permissions... i.e. move it from Party to Webtools). Jacopo > Abdullah Shaikh wrote: >> Chris, I guess you mean to simplify the things, but then Ofbiz doesn't force >> to use all components, user can use only the required components and can >> ignore the rest. >> >> As you said, probably party management, maybe someone else wants to only >> order management or only ecommerce, so if all the components are there, user >> can decide which one to use. >> >> -Abdullah >> >> On Fri, Nov 13, 2009 at 3:12 PM, Christopher Snow < >> sno...@snowconsulting.co.uk> wrote: >> >> >>> If a company start using ofbiz for small applications using just the >>> development framework, they can be very productive within a few weeks. >>> However, if they have to take on board the whole of ofbiz (i.e. the >>> components) before they get started, that is a huge task that may put them >>> off using ofbiz. >>> >>> If ofbiz followed the modular approach using maven, companies could start >>> using ofbiz core (+ probably party management), and then use more and more >>> of the other components as they get more experienced. >>> Charles TJ - SELC Sales Div wrote: >>> >>> >>>> I am agree with you Chris, the OFBiz is an excellent framework; >>>> OFBiz is like "The Beauty and The Beast". >>>> The Beast for the newcomers, but if we understand the framework, >>>> you will find "The Beauty of the OFBiz". >>>> >>>> - Charles TJ >>>> >>>> >>>> -----Original Message----- >>>> From: Christopher Snow [mailto:sno...@snowconsulting.co.uk] >>>> Sent: 13 Nopember 2009 15:18 >>>> To: user@ofbiz.apache.org >>>> Subject: Re: OFBiz in Canada? >>>> >>>> >>>> Ofbiz is an excellent application development framework. I think that any >>>> efforts that would focus on selling this aspect would attract newcomers to >>>> the project. In the past, I have recommended ofbiz as a development >>>> framework to a few architects and senior developers that I have worked >>>> with. >>>> When they take a look at the ofbiz site, their first reaction is to reject >>>> ofbiz as they think it is just another ecommerce application. >>>> >>>> I know a few of the users on the mailing list would like to see the core >>>> development framework of ofbiz separated from the other components. >>>> >>>> It would be interesting to know how many of the committers for ofbiz that >>>> DON'T use ofbiz primarily for ecommerce. I think that would be the main >>>> stumbling block to separating the core development framework. >>>> >>>> There are some interesting areas being worked on that such as Hans >>>> Bakker's BIRT implementation and /Jacques Le/ Roux Axis integration for >>>> complex types that will give the development framework even more power. >>>> >>>> >>>> >>>> >>> >> >> >
